We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
v20.3.0
Microsoft Windows NT 6.1.7601 Service Pack 1
No response
use node -v on Windows Server 2008 R2 Enterprise cmd.
node -v
I try to use pnpm use-node-version function to set Node.js version
use-node-version
the scripts of package.json:
"scripts": { "a": "node -v" }
The result of my test is this:
If the version number is less than 20.3.0, it won't throw an error.
Always
Expect the command node -v to produce the output correctly.
> node -v ELIFECYCLE Command failed with exit code 3221225785
The text was updated successfully, but these errors were encountered:
Support for Windows Server 2008 was removed in #31954
Sorry, something went wrong.
No branches or pull requests
Version
v20.3.0
Platform
Microsoft Windows NT 6.1.7601 Service Pack 1
Subsystem
No response
What steps will reproduce the bug?
use
node -v
on Windows Server 2008 R2 Enterprise cmd.I try to use pnpm
use-node-version
function to set Node.js versionthe scripts of package.json:
The result of my test is this:
If the version number is less than 20.3.0, it won't throw an error.
How often does it reproduce? Is there a required condition?
Always
What is the expected behavior? Why is that the expected behavior?
Expect the command
node -v
to produce the output correctly.What do you see instead?
Additional information
No response
The text was updated successfully, but these errors were encountered: