Hi @arcanis , I'm curious about this and some questions

• Which alternatives users will have?
• What's exactly the error that stop Vue to use yarn? (I'm asking mostly for some context)

:)

To better understand the problem, consider that --registry specifies the registry to use for the command currently running - and only this one. Now what happens when you then run yarn install a second time?

Does it make sense for this second install to potentially fail because the wrong registry is set? Even more insidious, what will happen if we need to clone a git dependency to complete the initial install? Should the git dependencies own dependencies (required to run the prepack script) be also fetched using the proxy?

In essence, the problem is that --registry defines a setting for exactly one session, but in practice that's almost never what you want. So instead in the v2 there are different ways we recommend to configure a registry:

• If you want to set the registry for your project, use a .yarnrc.yml file and define the registry using npmRegistryServer. This will guarantee that every Yarn command will use the exact same registry.

• If you want to set the registry for the whole computer, do the same thing but put your .yarnrc.yml file inside your $HOME directory. This will ensure that it'll be used by default (unless projects override it).

• If you want to set the registry for your shell session only, export YARN_NPM_REGISTRY_SERVER in your environment. Yarn will use it over whatever has been defined in the .yarnrc.yml files.

• If you really, really, really want to only do this for a single command, you can still use the environment variable approach (YARN_NPM_REGISTRY_SERVER=https://... yarn install). This makes it clear that the registry setting will also affect any Yarn invocation down the road, like the git case I mentioned.

What's exactly the error that stop Vue to use yarn? (I'm asking mostly for some context)

Yarn 2 is strict regarding extraneous options. Where the v1 was tolerating and ignoring them, the v2 will refuse to execute the command (this is because we can't know if the option is meant to have an argument or not, and thus our parsing may be completely wrong).

In this case --registry was automatically added to every install, causing them to fail when running yarn dlx @vue/cli init foo. They have a fix in the pipe, but until them we can afford to simply add a warning.