Skip to content

Handle PendingMigrationError from VS Code extension API breaking change #551

@blink-so

Description

@blink-so

Issue Description

Users are experiencing PendingMigrationError when using the Coder Remote extension with newer versions of VS Code. This appears to be related to a breaking change in the VS Code extension API where navigator is now a global in Node.js.

Error Details

PendingMigrationError: navigator is now a global in nodejs, please see https://aka.ms/vscode-extensions/navigator for additional info on this error.
    at get (file:///Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:361:1437)
    at Object.<anonymous> (/Users/sergei.zenin/.vscode/extensions/ms-vscode-remote.remote-ssh-0.120.0/out/extension.js:2:486184)
    at 19534 (/Users/sergei.zenin/.vscode/extensions/ms-vscode-remote.remote-ssh-0.120.0/out/extension.js:2:504894)

Context

Potential Solutions

  1. User workaround: Add setting "extensions.supportNodeGlobalNavigator": true to VS Code settings.json
  2. Extension fix: Update the extension to handle the new Node.js global navigator properly

Impact

Users report being stuck on "downloading vs code server" when connecting to workspaces through both Coder Desktop and the web UI.

Environment

  • VS Code: 1.101.2 (1.102 available)
  • Remote SSH: 0.120.0
  • Coder Remote: 1.9.2

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