Maël Nison

This isn't possible. Each package manager has different implementations of `run` unique to their implementation details, which Corepack couldn't replicate without becoming a package manager, which is out of scope...

I think @demurgos' point was that postinstall scripts find it difficult to execute scripts in a portable way across package managers (in a way that whatever package manager is used...

> Ideally, this feature would be exposed like `node --run ` Running scripts depend on knowledge unique to each package manager, so it couldn't be in Node (at best it...

> @arcanis has this pattern ever been problematic for Yarn? The situation is different - Yarn is a single program, so even if there's a conflict between its commands and...

Seems it's still a little too soon for that (trying to build a snapshot from Yarn)

I've implemented a first draft in #26

Indeed, having some way to configure that would be nice. I don't think however reading the `.npmrc` would be the best option; it's an npm-specific file, and I'm not fond...

Not really, the 1.x PnP implem was an experiment branch we never bumped to production. The amount of people who care about that is small.

> In terms of security risk, it’s similar to npx prior to NPM 7: > > - It obfuscates what action the user is actually performing > - It executes...

> patch it so that at least it never writes to `/usr` (next to `node` binary) Is there another place where the binaries would be available in the users' PATH...