pnpm doesn't respect use-node-version setting for pnpm install when using pnpm workspace

[antitoxic]

Verify latest release

• I verified that the issue exists in the latest pnpm release

pnpm version

8.6.12

Which area(s) of pnpm are affected? (leave empty if unsure)

CLI

Link to the code that reproduces this issue or a replay of the bug

https://github.com/antitoxic/pnpm-workspace-use-node-version-bug

Reproduction steps

1. Run:

   pnpm env use --global 18.15.0
   pnpm env use --global 16.19.1

2. Now your current node version globally should be 16.19.1 but you should have 18.15.0 installed as well.
3. Check out https://github.com/antitoxic/pnpm-workspace-use-node-version-bug and just run pnpm install

Describe the Bug

As the title says, it seems like after using pnpm workspace, pnpm install no longer respects theuse-node-version setting.

The same .npmrc config works fine when NOT using pnpm workspace.

Expected Behavior

I expect running pnpm install within a pnpm workspace to respect the use-node-version and automatically use the already available node version specified by use-node-version

Which Node.js version are you using?

18.15.0

Which operating systems have you used?

• macOS
• Windows
• Linux

If your OS is a Linux based, which one it is? (Include the version if relevant)

No response

[KSXGitHub]

Since you didn't describe the "Actual behavior", I have to ask you: Is this the same behavior you observed?

[antitoxic]

Hi @KSXGitHub , yes this is the error I'm getting.