Access to the binaries without global install

[aduh95]

I wonder if it would be possible to have a feature similar to python -m pip to access the package manager binaries without having them on the path. It would be useful in case the binary name clashes with another program. That could potentially address the concern of "How Corepack scales if there's 1000 package managers added to it, each package manager adding 100 binaries to the path?".

The API could look something like:

> corepack yarn install

wdyt?

[arcanis]

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 🤔

[aduh95]

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).

[arcanis]

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.