Corepack with Yarn commands version diffrences

[itayking1990]

Hey,

I started to use yarn with corepack I have the latest nodeJS LTS build and I made sure to use corepack enable command.

I am not sure what is going on but after enabling corepack I have a "global" yarn version 1.22.19 if I am outside of a project and I check yarn -v I see version 1.22.19

I know I can change it using corepack install -g to update this "global" yarn but it does not matter because the problem is when I am trying to create a new project with yarn init, it installs yarn 4.x.x aka the latest stable version of yarn why is it?

I get this which is strange I thought it should use the "global" yarn version which is 1.22.19 but instead, it uses the latest stable 4 version :

[arcanis]

That's expected. New projects are created using the latest release of Yarn (ie init sets packageManager to 4.x).

On the other hand, we keep 1.x as the global binary to avoid breaking older Yarn projects which didn't define any packageManager field.

[itayking1990]

I understand. So, if I were to run an old yarn project that uses classic yarn without packageManager, it would access the global binary am I right?

If I were to update it (the global binary) to version 4 using Corepack install global, would it still access the global binary? what would happen then?

from Corepack docs:

And how can I choose the version to init yarn with for the new project?
for example, I would like one project to use the latest version 1 and another project to use the latest version 3.x.x

[arcanis]

If I were to update it (the global binary) to version 4 using Corepack install global, would it still access the global binary? what would happen then?

Running corepack install -g [email protected] won't affect the behaviour of yarn init, which will always set packageManager to the latest version. The global version will only ever be used with projects that have no configured packageManager field.

And how can I choose the version to init yarn with for the new project?

You can call yarn init -i=1.22.22, or you can call corepack use yarn@^1 in your new folder after it got created. Alternatively you can always edit the package.json yourself to refer to whatever version you wish to use.

[itayking1990]

Thank you so much for taking the time to explain this to me in detail!

I wish Yarn docs would be better with example for each command =/