Zoltan Kochan

As you can see in [this post](https://github.com/openjs-foundation/package-metadata-interoperability-collab-space/issues/15#issuecomment-2312980507) from past core npm maintainer, he suggests to not allow build scripts to pick the runtime.

he says they consider postinstall scripts a 'legacy feature' and don't want us to make it easier using it.

I want to add this feature to pnpm v10 because I want it to be able to install pnpm v11 with the specified node.js version. That would allow us to...

The proposed solution with engines.runtime was released in pnpm v10.21

No, I have not risked to make a switch. I have used a workaround to make https-proxy-agent work: https://github.com/pnpm/components/commit/02d17cc303c94dc7d85458fd233303edcc452c8b

@KSXGitHub could the checksum of the `.pnpmfile.cjs` differ in different envs?

@divmgl do you have the same `.pnpmfile.cjs` file both locally (when you create the lockfile) and in the docker, when you run `pnpm install --frozen-lockfile`?

I guess if git changes the line endings, the checksum could differ

Maybe we could ignore the pnpmfileChecksum check if `--frozen-lockfile` is used and `.pnpmfile.cjs` is not present. (or add a new flag, I don't know which is better)

>> (or add a new flag, I don't know which is better) > > I think adding a flag makes more sense here since we're having these issues in cases...