Skip to content

fix: add shell: true to npm spawn for Windows compatibility#2

Open
emorfiqberger wants to merge 1 commit intoUnlikeOtherAI:mainfrom
emorfiqberger:fix/windows-npm-spawn-enoent
Open

fix: add shell: true to npm spawn for Windows compatibility#2
emorfiqberger wants to merge 1 commit intoUnlikeOtherAI:mainfrom
emorfiqberger:fix/windows-npm-spawn-enoent

Conversation

@emorfiqberger
Copy link
Copy Markdown

Summary

  • On Windows, spawn('npm', ...) in launchProcesses() fails with ENOENT because npm is a .cmd file and Node.js spawn without shell: true cannot locate it.
  • Added shell: true to the WebUI spawn options to resolve the issue.

Test plan

  • Verified fix on Windows 11 — steroids web launches without spawn npm ENOENT error

🤖 Generated with Claude Code

On Windows, `spawn('npm', ...)` fails with ENOENT because npm is
a .cmd file. Adding `shell: true` resolves this by spawning through
the system shell, which correctly locates npm.cmd.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant