Access to the binaries without global install about corepack HOT 3 CLOSED

I think dropping the requirement is a good idea 👍 it's more that corepack <pkg manager> <binary> was a bit of an implementation detail so I didn't look too deep into its API, but it certainly makes sense. I'll make a PR to simplify that, and add it to the documentation.

from corepack.

It's already possible, except that you need to make the package manager name explicit, like this:

corepack yarn[@x.y.z] yarn install

Making it optional shouldn't be too difficult though 🤔

from corepack.

I suppose the reason for requiring to repeat the name of the package manager is to support package managers with several binaries, right? Considering that most package managers use only one binary – or use several binaries as a shortcut for a command available in the "main" one (such as npx <~> npm exec), I think it would make sense to drop this requirement. (Unless it may break something somewhere, in that case, it's certainly not worth the risk of breakage).

from corepack.