-
Notifications
You must be signed in to change notification settings - Fork 331
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
Calls to spawn that include '.cmd' or '.bat' on windows should include '{shell: true}' argument #1429
Comments
Hi, thanks for reporting. If there is a Windows user that would like to test a fix and open a PR that would be helpful. |
Will set something up locally and do a thingy |
Any update? I can't use ncu on windows after updating node above v18.12.0. |
Apologies work got intense and I forgot about this. Busy testing a fix now and will submit a PR once I confirm that it works on both windows and non-windows |
@cakidnyc would you mind testing this PR on your side? Seems to be working fine on Mac and Windows here |
It's good for me now on Windows 11 w/ node 20.16.0, thanks! It does turn out that I had to manually delete ncu first ( npm install -g npm-check-updates didn't seem to upgrade it and uninstall -g wasn't clearing it out either). After the manual delete and reinstall, then it starting working. So, it might be that it actually was working earlier, my install was just messed up. |
This is due to the recent security patch released by node.js: https://nodejs.org/en/blog/vulnerability/april-2024-security-releases-2
Steps to Reproduce
Current Behavior
EINVAL error is thrown
Expected Behavior
Command is executed
The text was updated successfully, but these errors were encountered: