getBundledCliPath() resolves @github/index.js (one dir too high) on Node with import.meta.resolve #1849

Activity

1. devm33

   transferred this issue fromgithub/copilot-clion Jun 30, 2026
2. github-actions

   added

   questionFurther information is requestedFurther information is requested

   on Jun 30, 2026
3. github-actions commented on Jun 30, 2026

   

   github-actionsbot

   on Jun 30, 2026 – with GitHub Actions

   Contributor

   More actions

   Investigation Results

   Thanks for the detailed report. After analyzing the code and verifying against the published npm packages, this does not appear to be a bug — the current behavior is correct. Reclassifying as a question.

   What I investigated

   Code path: nodejs/src/client.ts — getBundledCliPath() (line 366)

   What the code actually does

   The issue describes the problematic resolution as using @github/copilot/sdk, but the actual current code uses platform-specific packages via getCliPlatformPackageNames(). On Windows x64 that returns @github/copilot-win32-x64; on macOS arm64 it returns @github/copilot-darwin-arm64. It is not resolving @github/copilot at all.

   Why the dirname math is correct

   I verified against the live npm registry that the platform packages export sdk as ./sdk/index.js (a file inside a subdirectory):

   "./sdk": {
     "types": "./sdk/index.d.ts",
     "import": "./sdk/index.js"
   }
   

   So with sdkPath = .../node_modules/@github/copilot-darwin-arm64/sdk/index.js:

   • dirname(sdkPath) → .../node_modules/@github/copilot-darwin-arm64/sdk
   • dirname(dirname(sdkPath)) → .../node_modules/@github/copilot-darwin-arm64``
   • Result → .../node_modules/@github/copilot-darwin-arm64/index.js ✅

   This is the correct package root. The CJS fallback branch produces the same target path (join(base, ...packageName.split("/"), "index.js")), so both branches agree.

   Why the @github/index.js error would not occur with current code

   That error would only arise if the sdk export pointed to a file at the package root level (e.g. sdk.js not sdk/index.js), requiring only one dirname instead of two. The actual packages use ./sdk/index.js in a subdirectory, so two dirname calls are correct. The thin loader package (@github/copilot) has no exports at all and is never touched by this code path.

   Conclusion

   The code is working as designed. If you are encountering Copilot CLI not found errors in practice, it may be due to a corrupted/partial package installation or a non-standard module resolution environment. The documented COPILOT_CLI_PATH env var workaround bypasses this resolution entirely.

   Generated by Bug Handler for issue #1849 · sonnet46 1.3M · ◷
4. patniko commented on Sep 8, 2026

   

   patniko

   on Sep 8, 2026

   Contributor

   More actions

   Closing as fixed after verification against the current public SDK sources and bundled behavior.

   Public evidence

   • #2395 — Launch managed SDK servers through the Rust runtime wrapper (merged 2026-09-01)
   • #2463 — Use Copilot CLI releases for Node runtime (merged 2026-09-03)
   • commit 538b2dce3075 — Launch managed SDK servers through the Rust runtime wrapper (Launch managed SDK servers through the Rust runtime wrapper #2395)
   • commit ec1c6f4b6368 — Use Copilot CLI releases for Node runtime (Use Copilot CLI releases for Node runtime #2463)
   • nodejs/src/runtimeArtifacts.ts — ensureRuntimeBundle; getRuntimePackageName
   • nodejs/test/runtimeArtifacts.test.ts — resolves the installed platform runtime without network access
   • nodejs/test/runtimeArtifacts.test.ts — uses the SDK platform package namespace

   The reported behavior/request is implemented at the current SDK baseline, so this issue is being closed as completed.

   Public SDK baseline: github/copilot-sdk d5c9d06d8c41.
5. patniko

   closed this as completedon Sep 8, 2026