Support Yarn 2+ in lambda build with Amplify CLI

[rokoucha]

Is this feature request related to a new or existing Amplify category?

function

Is this related to another service?

No response

Describe the feature you'd like to request

Amplify CLI currently does not support Yarn 2+ in lambda build (background is written in #7883 (comment)) but an issue that adds support Yarn 2/3 is not created yet.

Describe the solution you'd like

Support Yarn 2+ in lambda build with Amplify CLI.

Describe alternatives you've considered

PnP support is not a must. Yarn 2+ have more useful functions besides that and is fast.

Additional context

No response

Is this something that you'd be interested in working on?

• 👋 I may be able to implement this feature request

Would this feature include a breaking change?

• ⚠️ This feature might incur a breaking change

[simlevesque]

In the meantime, you can rename your .yarnrc.yml into anything else, push, then revert. If you don't have to push functions often this is bearable. Someone could script this easily.

[NaomiGilbertE22]

In the meantime, you can rename your .yarnrc.yml into anything else, push, then revert. If you don't have to push functions often this is bearable. Someone could script this easily.

Thank you, I was racking my brain as to how am I supposed to un-migrate my whole project for a single deployment. Worked like a charm.

[neuquen]

In the meantime, you can rename your .yarnrc.yml into anything else, push, then revert. If you don't have to push functions often this is bearable. Someone could script this easily.

@simlevesque Could you explain what is happening with yarn by doing this?

[rafaelfaria]

Any progress on this? has been a couple years now. I am having issues with the latest yarn now.