Fix Node 20.12.2 child_process.spawn .cmd EINVAL on Windows #1455
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #1453 incompatibility with Node 20.12.2 on Windows. https://nodejs.org/en/blog/vulnerability/april-2024-security-releases-2
I looked for all usages of
child_process.spawn
which invoked a.cmd
file and addedshell: true
(conditionally since I didn't want to change non-Windows behavior)I also wrapped the
NPX_PATH_ESCAPED
because the path will contain spaces e.g.C:\\Program Files\\nodejs\\npx.cmd
which doesn't work withshell: true
There were other usages of
child_process.spawn
which were forffmpeg
andffplay
which I don't think needs any change since those are.exe
files.