In our next release v1.92, we will update to Electron 30 which includes Node.js 20.14.0. This Node version contains a breaking change, in response to a CVE, which may affect you if you execute .bat or .cmd files on Windows. Based on a simple scan of your extension's source code, you may be impacted by this change. The stable VS Code that contains this update will be released in early August.
Action: please try out your extension on this month's VS Code Insiders on Windows. If you are affected by this change, you will encounter an EINVAL error when you try to spawn a bat/cmd file.
Node.js has added a section on batch file spawning to their documentation. To fix any issues:
Find locations where you call child_process.spawn to execute a batch file on Windows
Add shell: true or shell: process.platform === 'win32' to the options object
If the batch script path may contain spaces, you will also need to wrap the path in quotation marks.
Please let us know if you run into issues or if you need clarification.
Hello from the VS Code team 👋
In our next release v1.92, we will update to Electron 30 which includes Node.js 20.14.0. This Node version contains a breaking change, in response to a CVE, which may affect you if you execute
.bator.cmdfiles on Windows. Based on a simple scan of your extension's source code, you may be impacted by this change. The stable VS Code that contains this update will be released in early August.Action: please try out your extension on this month's VS Code Insiders on Windows. If you are affected by this change, you will encounter an
EINVALerror when you try to spawn a bat/cmd file.Node.js has added a section on batch file spawning to their documentation. To fix any issues:
child_process.spawnto execute a batch file on Windowsshell: trueorshell: process.platform === 'win32'to the options objectPlease let us know if you run into issues or if you need clarification.
Happy coding!