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
engines.node
in package.json
is not working as expected
#3673
Comments
I can reproduce this with my machine Arch Linux x86_64 5.10.75-1-lts
nvm 0.39.0
npm 8.1.0
node v16.13.0
pnpm 6.19.1 Using This keeps me from using |
I know about this issue. I filed #3785 to fix it |
zkochan
added a commit
that referenced
this issue
Nov 11, 2021
1 task
zkochan
added a commit
that referenced
this issue
Nov 11, 2021
zkochan
added a commit
that referenced
this issue
Nov 12, 2021
Still reproduces with latest version |
needs to be reopened, the PR unfortunately did not fix this, or subsequent changes caused the issue to return. |
This is probably fixed by #4780 |
🚢 7.1.5 and 6.32.17 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
pnpm version: 6.13.0
Code to reproduce the issue:
My Node.js version: v16.6.2
My pnpm version: 6.13.0
What's in my
package.json
:Expected behavior:
When I run
pnpm start
, there shouldn't be any errors or warnings.Actual behavior:
When I run
pnpm start
, I got this warning:I guess it's probably because when I run npm scripts, it uses the
node
executable bundled in thepnpm
, instead of thenode
executable I installed in the OS?The text was updated successfully, but these errors were encountered: