Kristoffer K.

Node.js v20.6 [changed the ESM loader a bit](https://github.com/nodejs/node/pull/47999) so the version of Yarn used by Corepack needs to be updated to a version containing https://github.com/yarnpkg/berry/pull/5677. Fixed by https://github.com/nodejs/corepack/pull/308.

I also tested migrating to `node:test` (https://github.com/nodejs/corepack/pull/357) but didn't finish it as, in my opinion, https://github.com/nodejs/corepack/pull/349 provides a better experience.

> It's too bad the https://github.com/zertosh/v8-compile-cache/pull/47 isn't getting merged, though That PR isn't correct though, it resolves the specifier using `require.resolve` instead of `import.meta.resolve`. Doing it correctly would probably require...

Have you run `corepack enable`? Your reproduction is missing it; ```console $ docker run --rm node:16.17.1 bash -c "corepack prepare [email protected] --activate; pnpm -v" Preparing [email protected] for immediate activation... bash:...

Context for this issue: https://github.com/yarnpkg/berry/pull/4850#issuecomment-1295260539 > That sounds like a bug to me Indeed, ideally it should only do that if the version it would have used doesn't support `dlx`.

> @merceyz Why not? Reproducibility, if a project is installable and works today it should work in a year, if a range is used that might not be the case...

That command would set the `package.json#packageManager` field to a specific version of npm, not a range.

> but it'd imo be reasonable to allow arbitrary urls As build metadata or in general? I don't think we should allow using anything but `name@semver` as it would break...

Just to note: you can use Yarn v2 with `node_modules` as a stepping stone, just run `yarn config set nodeLinker node-modules`. > Let facebook deal with that, they are staffed...

> I understand prettier is a neat tool to remove discussions about the "proper" coding style, but I think the rules we have put us in a nice place already,...