Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Error when running nodejs app (npm test)

See original GitHub issue

Debugger listening on ws://127.0.0.1:46185/05be73ee-cc53-4636-a999-1de2510d7945
For help, see: https://nodejs.org/en/docs/inspector
Debugger attached.
Error in the js-debug bootloader, please report to https://aka.ms/js-dbg-issue: Error [ERR_INSPECTOR_ALREADY_ACTIVATED]: Inspector is already activated. Close it with inspector.close() before activating it again.
    at Object.inspectorOpen (inspector.js:137:11)
    at bootloader.bundle.cdp:7:4964
    at bootloader.bundle.cdp:7:6191
    at Object.<anonymous> (bootloader.bundle.cdp:7:6391)
    at r (bootloader.bundle.cdp:1:110)
    at bootloader.bundle.cdp:1:902
    at Object.<anonymous> (bootloader.bundle.cdp:1:912)
    at Module._compile (internal/modules/cjs/loader.js:1063:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1092:10)
    at Module.load (internal/modules/cjs/loader.js:928:32

Issue Analytics

State:
Created 2 years ago
Comments:5 (3 by maintainers)

Top GitHub Comments

1reaction

connor4312commented, Mar 25, 2021

Okay, thanks. It sounds like you’re using auto attach. In this case, you’ll want to run just node first (once) so update the bootloader, either using the nightly VS Code build or in the next version of VS Code that will come out next week.

0reactions

strarsiscommented, Mar 22, 2021

OK, so I use latest stable VSCode on WSL 2 on Windows 10.

git cloned the svgo repository, opened it in VSCode.
Switched to latest node version in VSCode terminal (nvm use lts/*) (v14.16.0).
Installed the dependencies (npm install).
Finally I invoked npm test. Here the debugger attaches and logs the error.