Freeze yarn to 1.21.1

[rhymes]

What type of PR is this? (check all applicable)

• Refactor
• Feature
• Bug Fix
• Optimization
• Documentation Update

Description

As mentioned in Introducing Yarn 2 ! on DEV by its maintainer and by @abenettt in #5740 Yarn 2 is out, and we don't support it, thus running the risk of breaking something in the future when Yarn 2 will be the default install.

As mentioned in the article:

If you don't want to upgrade all of your projects, just run yarn policies set-version ^1 in the repositories that need to stay on Yarn 1, and commit the result. Yarn will always prefer the checked-in binaries over the global ones, making it the best way to ensure that everyone in your team shares the exact same release!

I did just that, we can revisit which yarn version and how to upgrade to 2 in the future, in the meantime we should enforce this

Related Tickets & Documents

• Yarn 2 breaks application #5740
• Enforcing Yarn’s version across your project

[abenerd]

@rhymes I tried this too but when I executed the file to get the version like

 .yarn/releases/yarn-1.21.1.js --version

I got told I'm on yarn 2.0.0-rc.27

[rhymes]

@abenettt I think this change is to make sure yarn install picks up the correct yarn.

What happens if you exit the terminal, go into the directory again and type yarn -v ?

[abenerd]

@rhymes I'm having the same result then.

[rhymes]

@abenettt mmm how did you install Yarn 2 then?

[abenerd]

@rhymes Aaaaah I ran

yarn policies set-version berry

in my home directory and apparently as the repo lies within a child directory it takes precedence. Now that I removed it, it works again.

[maestromac]

I wonder how long until yarn 2 is compatible with most projects

[nickytonline]

LGTM 🚢

[nickytonline]

LGTM 🚢