Maël Nison

Which is what we do as well, I don't think that's the problem here? If there was a literal dependency on `node` we would have to respect it (and that...

> Put another way, this isn't behavior npm has, and it works fine with npm, so if it's not working with yarn, I'm not clear on why that's a bug...

Note that in most (all?) such cases, the problem is that the application is using an unsafe pattern *when a safe alternative is available.* Of course if there was absolutely...

Because everything that Yarn spawns must use the same Node release, otherwise some dependencies will work and others won't, cf the case I mentioned above with native dependencies. By contrast...

I'm be a bit concerned about degrading the perf in order to fix something that only affect a very small part of our users 😐 Maybe a compromise would be...

That sounds like a good idea, although I'd tend to prefer exposing each data result as a separate command (rather than options). I'd probably go with an interface like this:...

> Would it just modify the output order? Yep exactly - although perhaps that could be a different `yarn workspaces sort` command 🤔 > might leave `changeset` for someone else...

> Observe: the promise never resolves. You can't even terminate NodeJS using Ctrl+C. You have to kill it. I don't repro that; is something missing? 🤔 Outside of that, did...

> if i set `nodeLinker: node-modules` the promise gets resolved, doesn't matter which node version it is in this case. > Doesn't that mean it's yarn pnp related? Yes and...

The relevant error here is visible when running `yarn unplug eslint-plugin-prettier` inside the repository. After that, the REPL starts to properly reject the promise with an `ERR_MODULE_NOT_FOUND` not found. Digging...