Notification of breaking api change with v1.92 release of VS Code

[deepak1556]

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 .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:

1. Find locations where you call child_process.spawn to execute a batch file on Windows
2. Add shell: true or shell: process.platform === 'win32' to the options object
3. 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.

Happy coding!

[neutraali]

This is currently breaking the flow-for-vscode for Windows users. On startup there's a popup that states that "Flow server stopped", and the output panel shows something like this:

[Error - 00:00:00 PM] Starting client failed
Error: spawn EINVAL
    at ChildProcess.spawn (node:internal/child_process:421:11)
    at Object.spawn (node:child_process:800:9)
    at path\to\vscode\extensions\flowtype.flow-for-vscode-2.2.1\build\index.js:1:156960

[dstorfer-cn]

This is currently breaking the flow-for-vscode for Windows users. On startup there's a popup that states that "Flow server stopped", and the output panel shows something like this:

[Error - 00:00:00 PM] Starting client failed
Error: spawn EINVAL
    at ChildProcess.spawn (node:internal/child_process:421:11)
    at Object.spawn (node:child_process:800:9)
    at path\to\vscode\extensions\flowtype.flow-for-vscode-2.2.1\build\index.js:1:156960

Hello Everyone,
For Windows users, it just doesn't work anymore.

Is there any chance this will be fixed? I see the last release was nearly two years ago so I'm worried it won't be. Honestly, I would try to update it myself but I have zero experience writing extensions and I wouldn't know the first thing about creating an environment to successfully run and test it. The change appears very small, but the rest looks like a mountain to me.

Thanks,
David