fix(nodejs): add .js extension to vscode-jsonrpc/node import in session.ts

[or2ooo]

Summary

• Add missing .js file extension to vscode-jsonrpc/node imports in nodejs/src/session.ts
• Matches the existing correct pattern in client.ts (from "vscode-jsonrpc/node.js")
• Same class of fix as Missing Module Error in SDK Versions 0.1.10 and 0.1.11 #8

Problem

SDK 0.1.31 added a new import to session.ts:

import { ConnectionError, ResponseError } from "vscode-jsonrpc/node";

Since the SDK declares "type": "module" (ESM) and vscode-jsonrpc@8.2.1 has no exports map, Node.js ESM resolution cannot resolve the bare subpath without the .js extension.

Error:

ERR_MODULE_NOT_FOUND: Cannot find module 'vscode-jsonrpc/node' imported from @github/copilot-sdk/dist/session.js

Fix

-import type { MessageConnection } from "vscode-jsonrpc/node";
-import { ConnectionError, ResponseError } from "vscode-jsonrpc/node";
+import type { MessageConnection } from "vscode-jsonrpc/node.js";
+import { ConnectionError, ResponseError } from "vscode-jsonrpc/node.js";

Fixes #707

[Copilot]

Pull request overview

Fixes a Node.js ESM runtime resolution failure in the Node SDK by aligning session.ts with the existing client.ts import pattern for vscode-jsonrpc.

Changes:

• Update vscode-jsonrpc subpath imports in nodejs/src/session.ts to include the .js extension for ESM compatibility.

[SteveSandersonMS]

Thanks for the contribution. This issue was already fixed by another commit, so I'll close it.