I guess the implementation would become easier with the setting placed inside package.json?

Maybe we could place useNodeVersion there instead

{
  "pnpm": {
    "useNodeVersion": "18.0.0"
  }
}

If we decide to proceed with .npmrc, I think we already read it for some settings, so no need to read it again. Like here:

https://github.com/pnpm/pnpm/blob/8920dbce383f6b50942f23c7d029da5f807af5ce/pkg-manager/plugin-commands-installation/src/recursive.ts#L187C10-L187C10

Thanks @zkochan

Manifests are available in the selectedProjectsGraph, I agree it's easier to pull it from there. Maybe that's what I should do for the first iteration.
But, ultimately, it'd be great to support both.

Memoization of the readLocalConfig happens in the same place it's consumed and I kinda need it in a different place. I'll see what I can do with it, but for the moment will focus on pnpm settings in the package.json.

Tests are needed.

Also, what about running install scripts of projects on pnpm install?

Tests are needed.

Also, what about running install scripts of projects on pnpm install?

Thanks @zkochan !

It's not complete yet. I still need to figure out tests randomly failing on CI (likely timeout related). I'll try to add some tests as well.

As pnpm install isn't recursive - either default or specified on the root-level version will be used. I see now that's incorrect, dependencies for those projects needs to be installed with the version they require.

Just a note - I can only work on this a few a week tops. Next month I might get more time for this, I really look forward getting it done though.

Sorry, not happening anytime soon. Closing to declutter for now.