-
Notifications
You must be signed in to change notification settings - Fork 262
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
Error: spawn EINVAL on Windows #715
Comments
Updated node-pre-gyp attempting to resolve this issue, but it is still unresolved upstream. For now, hack in a patch. Once upstream fixes this, we can update to the fixed version and drop this hack. For more details, see mapbox/node-pre-gyp#715
Updated node-pre-gyp attempting to resolve this issue, but it is still unresolved upstream. For now, hack in a patch. Once upstream fixes this, we can update to the fixed version and drop this hack. For more details, see mapbox/node-pre-gyp#715
Updated node-pre-gyp attempting to resolve this issue, but it is still unresolved upstream. For now, hack in a patch. Once upstream fixes this, we can update to the fixed version and drop this hack. For more details, see mapbox/node-pre-gyp#715
@benmccann any chance this could be picked up for 2.0? |
Does this happen on |
Should we just always set |
The change in node was specifically just for Windows and bat/cmd files so imo doing it just for Windows, like it was proposed, is fine |
The proposal does it for non-bat/cmd files in Windows though. If we're going to do it as minimally as possible perhaps we should check for that too |
I don't have a Windows system with access to the codebase where this happens, sorry |
The patch saves my day, but it will not work when node is installed in path containing space like |
It seems when using |
So one could just always escape the commands and arguments yet only set |
The latest versions of Node include a security vulnerability fix which now requires calling
spawn()
withshell: true
on Windows (Node security release blog).I'm currently working around this by using patch-package with the following patch:
The text was updated successfully, but these errors were encountered: