-
Notifications
You must be signed in to change notification settings - Fork 29.7k
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
child_process,Windows: deprecate explicit use of cmd.exe
#14157
Comments
@nodejs/platform-windows |
Technically, this is correct, and I don't see a chance of breaking code. Some will probably break due to custom child process environments, but that's what deprecation is for. |
So, for users, what this is effectively deprecating is using an environment without I'm -0 on this. While situations without But discussion is always welcome! |
|
Closing as it is inactive for around an year, feel free to re-open if there is anything outstanding. |
https://github.com/nodejs/node/blob/master/lib/child_process.js#L444 has a fallback to use
cmd.exe
in caseprocess.env.ComSpec
is falsy.This is redundant, fragile, and generally covers-up an invalid state (
%ComSpec%
should always be defined and point to a valid shell executable).This code path should be deprecated according to the guide at https://github.com/nodejs/node/blob/master/COLLABORATOR_GUIDE.md#deprecations
and https://github.com/nodejs/node/blob/master/doc/api/deprecations.md
Ref: #14149 (comment)
The text was updated successfully, but these errors were encountered: