Maël Nison

> That's determining version precedence, not subsumption, and I think it's the core of our misunderstanding I don't think there's a misunderstanding; we understand you believe your interpretation is the...

I'm still against dropping the check in any kind of "by default" behaviour. Using the wrong package manager for the currently installed project is broken and should be fixed upstream....

In theory, `$npm_execpath run` instead of `npm run`. Which gets tricky with Windows, so the easiest and most portable option is usually to make the install script a `.js` file...

Windows is a little weird, I think it sometimes locks files just after their creation for "malicious file analysis" 🙁

> How about adding something like “corepack --save [email protected]” that writes to the package.json? In the case of Yarn we have `yarn set version`. It doesn't currently save the hash,...

That seems a little out of scope, since it'd perform uncontrolled changes outside of the folders Corepack is supposed to work with. It would also be difficult to make it...

Something happened that caused the binary to be overwritten. It's not possible to say what for certain with the info you have, but Corepack doesn't remove them by itself, so...

And for `corepack install -g` (and this command only), `yarn` should alias to `yarn@^1`, not `yarn@*`.

Yeah, I think it's fine to keep it as a follow-up. I have another idea to make this process a little less magic, I'll handle that. > Heck, even https://www.npmjs.com/package/yarn...

> @arcanis and @merceyz, would you be happy with instead [reifying the version on `corepack install`](https://github.com/nodejs/corepack/pull/300/commits/6cf4ea9bbe0cf0d2f2ed04c3b00007ba1b1fe38c) as I previously had? Not sure what you mean by that - as far...