Skip to content

Clarify the interaction of useNodeVersion/executionEnv.nodeVersion and nodeVersion in settings documentation #667

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
sdavids opened this issue May 22, 2025 · 0 comments

Comments

@sdavids
Copy link

sdavids commented May 22, 2025

https://pnpm.io/settings#usenodeversion

https://pnpm.io/settings#executionenvnodeversion

https://pnpm.io/settings#nodeversion

If you want to prevent contributors of your project from adding new incompatible dependencies, use > nodeVersion and engineStrict in a pnpm-workspace.yaml file at the root of the project:

DRY:

useNodeVersion: 12.22.0
engineStrict: true
executionEnv:
  nodeVersion: 12.22.0
engineStrict: true

Or not DRY?

useNodeVersion: 12.22.0
nodeVersion: 12.22.0
engineStrict: true
executionEnv:
  nodeVersion: 12.22.0
nodeVersion: 12.22.0
engineStrict: true

node -v is executed after the useNodeVersion/executionEnv.nodeVersion has been installed therefore an explicit nodeVersion is unnecessary?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant