Roo Extension Crash After VS Code Update - `navigator` and `path.relative` Error

[jgkme]

App Version

v3.25.6

API Provider

Anthropic

Model Used

Claude 4.0 Sonnet

Roo Code Task Links (Optional)

No response

🔁 Steps to Reproduce

Mine too keep greying out while its performing some task randomly

VS Studio Version: 1.102.3 (user setup)
Commit: 488a1f239235055e34e673291fb8d8c810886f81
Date: 2025-07-29T03:00:23.339Z
Electron: 35.6.0
ElectronBuildId: 11847422
Chromium: 134.0.6998.205
Node.js: 22.15.1
V8: 13.4.114.21-electron.0
OS: Windows_NT x64 10.0.26100

Roo code version : roo-cline-3.25.6

Windows 11 24 H2 running on WSL2 Ubuntu with 8GB RAM and 8CPU

Model used : Gemini 2.5 Pro / Claude 4.0
Model Provider : via open router

So I asked Roo to go through the Developer Tool logs and generate a bug report

Subject: [BUG] Roo Extension Crash After VS Code Update - navigator and path.relative Errors

Description

The Roo extension (rooveterinaryinc.roo-cline) is consistently crashing after a recent Visual Studio Code update. The developer tools console shows two primary errors that are preventing the extension from functioning correctly.

Error 1: PendingMigrationError: navigator is now a global in nodejs

This error appears frequently and seems to be the main cause of the crash. It indicates a conflict with the newly introduced global navigator object in VS Code's extension host environment.

Stack Trace Snippet:

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, please see https://aka.ms/vscode-extensions/navigator for additional info on this error.
    at get (file:///home/username/.vscode-server/bin/488a1f239235055e34e673291fb8d8c810886f81/out/vs/workbench/api/node/extensionHostProcess.js:356:6146)
    at /home/username/.vscode-server/extensions/rooveterinaryinc.roo-cline-3.25.6/dist/extension.js:79:9406
    ...

Error 2: RangeError: path should be a 'path.relative()'d string

This error is specific to the Roo extension and occurs during file operations. It seems to be related to how file paths are being handled for protection checks.

Stack Trace Snippet:

ERR [Extension Host] Error checking protection for /home/username/.roo/rules: RangeError: path should be a `path.relative()`d string, but got "../../.roo/rules"
    at doThrow (/home/username/.vscode-server/extensions/node_modules/.pnpm/ignore@7.0.4/node_modules/ignore/index.js:557:9)
    at checkPath (/home/username/.vscode-server/extensions/node_modules/.pnpm/ignore@7.0.4/node_modules/ignore/index.js:576:12)
    at Dht._test (/home/username/.vscode-server/extensions/node_modules/.pnpm/ignore@7.0.4/node_modules/ignore/index.js:637:5)
    at Dht.ignores (/home/username/.vscode-server/extensions/node_modules/.pnpm/ignore@7.0.4/node_modules/ignore/index.js:720:17)
    at t.isWriteProtected (/home/username/.vscode-server/extensions/rooveterinaryinc.roo-cline-3.25.6/core/protect/RooProtectedController.ts:45:31)

Environment

• VS Code Version: VS Studio Version: 1.102.3 (user setup)
• Operating System: Ubuntu Linux (via WSL) Windows 11 24 H2
• Roo Extension Version: 3.25.6

Suggested Action

The extension's code likely needs to be updated to account for the new navigator global and to ensure that paths passed to the ignore library are correctly formatted.

Please let me know if you need any more information.

💥 Outcome Summary

just randomly crashing while doing some task

📄 Relevant Logs or Errors (Optional)

ERR [Extension Host] Error checking protection for /home/username/.roo/rules: RangeError: path should be a `path.relative()`d string, but got "../../.roo/rules"
    at doThrow (/home/username/.vscode-server/extensions/node_modules/.pnpm/ignore@7.0.4/node_modules/ignore/index.js:557:9)
    at checkPath (/home/username/.vscode-server/extensions/node_modules/.pnpm/ignore@7.0.4/node_modules/ignore/index.js:576:12)
    at Dht._test (/home/username/.vscode-server/extensions/node_modules/.pnpm/ignore@7.0.4/node_modules/ignore/index.js:637:5)
    at Dht.ignores (/home/username/.vscode-server/extensions/node_modules/.pnpm/ignore@7.0.4/node_modules/ignore/index.js:720:17)
    at t.isWriteProtected (/home/username/.vscode-server/extensions/rooveterinaryinc.roo-cline-3.25.6/core/protect/RooProtectedController.ts:45:31)

[roomote]

Hi @jgkme! I'm here to help out the maintainers and am going to see if I can fix this issue. The path validation error in the ignore library when checking file protection looks like the main culprit. I'll investigate and work on a fix. Thanks for the detailed bug report!

[roomote]

Hi @jgkme! I've created a pull request to fix this issue: #6584

The fix adds a check to handle paths outside the current working directory gracefully, preventing the RangeError from the ignore library. All tests are passing and CI checks have completed successfully.

The solution mirrors how RooIgnoreController handles similar cases, ensuring consistency across the codebase. Please let me know if you have any questions or feedback!

[jgkme]

How about the global navigator

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, please see https://aka.ms/vscode-extensions/navigator for additional info on this error.
    at get (file:///home/username/.vscode-server/bin/488a1f239235055e34e673291fb8d8c810886f81/out/vs/workbench/api/node/extensionHostProcess.js:356:6146)
    at /home/username/.vscode-server/extensions/rooveterinaryinc.roo-cline-3.25.6/dist/extension.js:79:9406
    ...