[BUG] PendingMigrationError: navigator is now a global in nodejs on code-server (RHEL 9.6, Offline Environment)

[zhushanhu]

Problem (one or two sentences)

The Roo Code extension (v3.38.0) fails to initialize on code-server v4.105.0 (VS Code v1.105.0) in an air-gapped RHEL 9.6 environment. The extension host crashes due to the new navigator global in Node.js 22+, and the UI (Settings button, chat) becomes completely unresponsive.

Context (who is affected and when)

Observed Error Logs (Browser Console)

The primary error causing the Extension Host to hang/crash:

ERR navigator is now a global in nodejs, please see https://aka.ms/vscode-extensions/navigator for additional info on this error.: PendingMigrationError: navigator is now a global in nodejs
    at get (file:///usr/local/code-server/lib/vscode/out/vs/workbench/api/node/extensionHostProcess.js:393:6610)
    at .../rooveterinaryinc.roo-cline-3.38.0/dist/extension.js:115:408

Followed by network timeouts due to the offline environment:

{
  "code": "ETIMEDOUT",
  "message": "Error fetching OpenRouter models",
  "stack": "AggregateError: Error\n at qne.from (.../dist/extension.js:170:14695)..."
}

Additional Context

1. Offline Issue: In an air-gapped environment, the extension seems to hang while attempting to fetch model lists (OpenRouter/Anthropic) during the initial load, with no way to enter Settings to switch to a local provider (like Ollama) because the UI is already frozen by the navigator error.
2. Compatibility: The same setup works fine on VS Code Desktop (Windows/macOS), but fails on code-server due to the specific way the Extension Host handles the navigator global in Node.js 22.

Reproduction steps

Environment
Operating System: RHEL 9.6 (Plow)

code-server version: 4.105.0 (VS Code v1.105.0)

Roo Code version: 3.38.0

Deployment: Bare-metal / Direct install

Network Status: Strictly Offline / Air-gapped (No internet access)

Steps to Reproduce
Install code-server 4.105.0 on an offline RHEL 9.6 server.

Sideload Roo Code 3.38.0 via VSIX.

Access via browser (ensuring isSecureContext is true).

The "Welcome to Roo Code" screen appears, but all buttons (Settings, etc.) are dead.

Expected result

run well

Actual result

the UI (Settings button, chat) becomes completely unresponsive

Variations tried (optional)

No response

App Version

3.38.0

API Provider (optional)

None

Model Used (optional)

No response

Roo Code Task Links (optional)

No response

Relevant logs or errors (optional)

[roomote]

I have analyzed this issue and identified the root cause.

Root Cause Analysis

The bundled extension.js contains 65+ references to navigator.userAgent, navigator.platform, navigator.userLanguage, and other navigator properties from several bundled dependencies:

1. debug package - uses navigator.userAgent for browser detection in its useColors() function
2. axios - uses navigator.userAgent via platform_default.navigator for browser environment detection
3. pdf-parse (via pdfjs) - uses various navigator properties for browser compatibility checks

In Node.js 22+ (which code-server v4.105.0 uses), navigator is now a global object. These dependencies check typeof navigator !== "undefined" which now returns true, then attempt to access properties like navigator.userAgent. VS Code's extension host intercepts these accesses and throws PendingMigrationError to help extensions migrate.

Important: This is a different issue from #6356, which was about bluebird accessing navigator.onLine. The bluebird override is already in place, but these other packages are now causing the same type of error.

Proposed Implementation Plan

Add a navigator shim/banner in the esbuild configuration that provides safe stub values before any other code loads. This will satisfy the browser detection checks while preventing the PendingMigrationError.

Specific changes:

1. Modify src/esbuild.mjs to add a banner option with JavaScript that creates a safe navigator stub:

banner: {
  js: `// Navigator shim for Node.js 22+ compatibility
if (typeof globalThis !== "undefined" && !globalThis._navigatorShimApplied) {
  const navigatorStub = {
    userAgent: "",
    platform: "",
    userLanguage: undefined,
    appName: "",
    appVersion: "",
    product: "",
    languages: [],
    hardwareConcurrency: 1,
    standalone: false,
  };
  globalThis.navigator = globalThis.navigator || navigatorStub;
  // Mark as applied to prevent double-application
  globalThis._navigatorShimApplied = true;
}`
}

2. This approach:
   • Provides safe default values for all commonly accessed navigator properties
   • Works for both the main extension and worker bundles
   • Does not interfere with VS Code's built-in functionality
   • Is compatible with both Node.js 20 and Node.js 22+

Please mention @roomote in a comment saying that you approve this plan, and I'll proceed with the implementation.

[zhushanhu]

@roomote approve this plan

[roomote]

Thanks for the approval! I'll proceed with implementing the navigator shim in the esbuild configuration. I'll open a draft PR shortly to share progress.

[roomote]

Opened a draft PR with my attempt at addressing this: #10400

The PR adds a navigator shim in the esbuild configuration that provides safe stub values for commonly accessed navigator properties (userAgent, platform, onLine, etc.) before any bundled code runs. This should prevent the PendingMigrationError on code-server with Node.js 22+.

Would appreciate if you could test the fix once the PR is ready. Feedback welcome!

[zhushanhu]

Thanks for the fix! I'm eager to test this, but I'm in an offline environment and unable to build it myself. Is there a way to download a test .vsix for this PR? I'll let you know the results as soon as I can test it on my server.