Skip to content

Windows workspace npm shims break the squad_state launcher #2544

Done

Description

@tamirdresher

Problem

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

  1. Put a workspace's node_modules\.bin containing the Squad CLI shim on PATH.
  2. Initialize a separate project without its own local CLI install, and leave SQUAD_CLI unset.
  3. 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

  1. added a commit that references this issue on Nov 19, 2026
    7226263
  2. added a commit that references this issue on Nov 19, 2026
    42b77f1
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions