We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Running node 20.12.2 + vsce 2.26.0 on windows, and publishing it gives error "spawn EINWAL"
I guess it executes npm.cmd
npm.cmd
see nodejs/node#52554 and https://nodejs.org/en/blog/vulnerability/april-2024-security-releases-2
workaround is to add { shell: true }
{ shell: true }
https://github.com/microsoft/vscode-vsce/blob/main/src/package.ts#L409
workaround: downgrading to node 20.12.1
The text was updated successfully, but these errors were encountered:
Yup, we started hitting this in our very own CI since almost a week.
@benibenj Can you take a look?
Sorry, something went wrong.
benibenj
Successfully merging a pull request may close this issue.
Running node 20.12.2 + vsce 2.26.0 on windows, and publishing it gives error "spawn EINWAL"
I guess it executes
npm.cmd
see nodejs/node#52554 and https://nodejs.org/en/blog/vulnerability/april-2024-security-releases-2
workaround is to add
{ shell: true }
https://github.com/microsoft/vscode-vsce/blob/main/src/package.ts#L409
workaround: downgrading to node 20.12.1
The text was updated successfully, but these errors were encountered: