Repository navigation
Squad installation fails #247
Description
Hello,
When running (either through a global npm install, or through npx directly), the current latest releases (as of writing), fails with the following error:
npx @bradygaster/squad-cli init
node:internal/modules/run_main:107
triggerUncaughtException(
^
Error [ERR_MODULE_NOT_FOUND]: Cannot find module '/var/home/marchermans/.npm-packages/lib/node_modules/@bradygaster/squad-cli/node_modules/vscode-jsonrpc/node' imported from /var/home/marchermans/.npm-packages/lib/node_modules/@bradygaster/squad-cli/node_modules/@github/copilot-sdk/dist/session.js
Did you mean to import "vscode-jsonrpc/node.js"?
at finalizeResolution (node:internal/modules/esm/resolve:271:11)
at moduleResolve (node:internal/modules/esm/resolve:861:10)
at defaultResolve (node:internal/modules/esm/resolve:988:11)
at #cachedDefaultResolve (node:internal/modules/esm/loader:697:20)
at #resolveAndMaybeBlockOnLoaderThread (node:internal/modules/esm/loader:714:38)
at ModuleLoader.resolveSync (node:internal/modules/esm/loader:746:52)
at #resolve (node:internal/modules/esm/loader:679:17)
at ModuleLoader.getOrCreateModuleJob (node:internal/modules/esm/loader:599:35)
at ModuleJob.syncLink (node:internal/modules/esm/module_job:160:33)
at ModuleJob.link (node:internal/modules/esm/module_job:245:17) {
code: 'ERR_MODULE_NOT_FOUND',
url: 'file:///var/home/marchermans/.npm-packages/lib/node_modules/@bradygaster/squad-cli/node_modules/vscode-jsonrpc/node'
}
Node.js v25.8.0
I am running on Node.js 25.8
There does not seem to be an obvious way I can fix it.
I running it natively by cloning the project and running it through a debugger and that works, but that does not seem to be an effective solution.
Any suggestions on how to proceed, any additional information you would like that would enable you to help me debug this?
Reacted by Michael S. Collier
Activity
donbing commentedon Mar 7, 2026
similar here, Node.js v24.13.0
bradygaster commentedon Mar 7, 2026
Thanks for reporting this, @marchermans! And @donbing for the additional data point.
Two separate module resolution issues are at play here:
1. \�scode-jsonrpc/node\ (Node 25.8)
This is an upstream issue in @github/copilot-sdk. Node 25 enforces stricter ESM resolution — \�scode-jsonrpc/node\ needs to be \�scode-jsonrpc/node.js. This needs to be fixed in the copilot-sdk dependency.
2. @opentelemetry/api\ (Node 24.13)
This is listed as a direct dependency of @bradygaster/squad-sdk, so it should be resolved during install. This might be an npm hoisting issue with
px\ not fully resolving transitive dependencies.
Workaround for now: Clone the repo and run locally (as you found). We'll investigate the packaging to ensure transitive deps resolve correctly with
px.
Node version note: Squad is actively tested on Node 22 LTS. Node 24/25 are bleeding edge — we'll work on compatibility but Node 22 is the safest bet for now.
Labeling this as a bug — we'll look into the packaging side.
EngstromJimmy commentedon Mar 7, 2026
I ran into the same issue as @marchermans.
I have narrowed the problem down to a @github/copilot-sdk@0.1.31 issue, if i run @github/copilot-sdk@0.1.30 it seems to work again
dfberry commentedon Mar 7, 2026
I'm hitting this on Node 22.14.0 on apple silicon
fix: make @opentelemetry/api import resilient + bump copilot-sdk (#247)
docs: update fenster history and decision for #247
bradygaster commentedon Mar 7, 2026
Fixed on dev (commits 46162a9, 896f14a). Three changes:
Made @opentelemetry/api import resilient — new \otel-api.ts\ wrapper with full no-op fallbacks. All 9 source files rewired through it. Telemetry gracefully degrades if packages aren't installed instead of crashing.
Added vscode-jsonrpc as direct dependency in both packages to improve npm hoisting for npx installs. The upstream ESM subpath resolution issue in @github/copilot-sdk still exists, but explicit dependency declaration helps npm resolve it.
Bumped @github/copilot-sdk to ^0.1.32 which has improved ESM compatibility.
These fixes will ship in the next release. In the meantime, Node 22 LTS is the recommended version.
docs(ai-team): Merge release-prep decisions
bradygaster commentedon Mar 7, 2026
Thanks for reporting this module resolution issue, @marchermans! The vscode-jsonrpc import path problem is frustrating, and we appreciate you working through debugging with us. We've got a fix in the works. Thanks for sticking with it! 🙏
— McManus 📝, on behalf of the Squad
craigb commentedon Mar 7, 2026
@bradygaster I think this issue is still present in 0.8.22:
feat: autocomplete + loop/triage/hire CLI commands (github#247, githu…
jspraul commentedon Mar 17, 2026
Per github/copilot-sdk#707 (comment) "Still present in v0.1.32, also reproducible on Node 22" (the thread has a couple workarounds)
Meanwhile using Windows Sandbox I've tested and confirmed that squad works out-of-the-box with npm in nodejs 22 and 25, but not pnpm or yarn.
🎉Success: NodeJS 25.8.1 npm (11.11.0) in Windows Sandbox
⚠Error using pnpm in Windows Sandbox (repro step 1 of 2: First PowerShell Window)
⚠Error using pnpm in Windows Sandbox (repro step 2 of 2: Next PowerShell Window)
⚠Error using pnpm in Windows Sandbox:
⚠Error using yarn in Windows Sandbox (repro)
⚠Error using yarn in Windows Sandbox: