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
{{ message }}
Repository navigation
Windows workspace npm shims break the squad_state launcher #2544
On Windows, a project using the generated Squad launcher can fail to start squad_state and fail squad doctor when PATH resolves squad.cmd from a workspace's node_modules\.bin directory. The launcher looks under .bin\node_modules instead of resolving the sibling installed package. The same layout affects a local npx.cmd fallback.
Reproduction
Put a workspace's node_modules\.bin containing the Squad CLI shim on PATH.
Initialize a separate project without its own local CLI install, and leave SQUAD_CLI unset.
Run squad doctor in the project.
The squad_state bridge exits with Cannot resolve the JavaScript entry. The published 2.0.0 launcher is affected. As a workaround, set SQUAD_CLI to the installed CLI's dist\cli-entry.js.
Expected
Resolve workspace shims to their sibling package entry points without invoking a shell or altering command arguments.
Activity
test: group Windows shim resolution cases
test: cover explicit Windows workspace shims