You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Follow-up to #442. The dispatch path is fixed (160e14e). Still POSIX-only: verify.js spawns /bin/sh -c, memory-sup.js probes 'which node', pathEnv.js defaults SHELL to /bin/zsh, devservers.js runs user commands. Each needs a win32 path or an honest no-op, all testable on macOS with the platform injected.
Merged into the #397 branch. verify.js uses Git Bash (bash -c) on win32 — the same POSIX shell the doctor probes for — because verify commands are POSIX and cmd.exe/PowerShell would mis-parse them; a missing bash is a real error, not a silent fallback. memory-sup.js reuses providers.defaultWhich. pathEnv.js is an explicit win32 no-op (there is no login shell of that kind) and no longer splits PATH on ':', which would have shredded C:\Windows\system32. devservers.js goes through cross-spawn for npm.cmd and kills the pid directly on win32. WSL-side projects route through the ssh.js seam in both verify and devservers.
Activity
currentbits commentedon Aug 18, 2026
Merged into the #397 branch. verify.js uses Git Bash (
bash -c) on win32 — the same POSIX shell the doctor probes for — because verify commands are POSIX and cmd.exe/PowerShell would mis-parse them; a missing bash is a real error, not a silent fallback. memory-sup.js reuses providers.defaultWhich. pathEnv.js is an explicit win32 no-op (there is no login shell of that kind) and no longer splits PATH on ':', which would have shredded C:\Windows\system32. devservers.js goes through cross-spawn for npm.cmd and kills the pid directly on win32. WSL-side projects route through the ssh.js seam in both verify and devservers.