30 support issues
- All
- Questions
- Suggestions
- Problems
Sergei Kardashev
Oct 6, 2023
the add-on won't work
I try to use the add-on for the first time. It won't work. I click the icon, I see the panel appears. It has a message next to Auto-Manual switch: 'Runaway tabs were detected and Auto mode was disabled. If the condition persists, please file a bug report.'
Garfield Doe
Jan 20, 2022
Don't open in a tab
Hi :)
I'm used to this workflow:
Starting my tests, open devtools via F12 and waiting for the green extension icon to appear. Then clicking on it and hit enter to let the test start.
But since today my chrome opens the node.js devtools in a tab and everytime I want to close it it opens it again immediately.
Is there a setting to prevent that from happening?
Karlos Smith
May 24, 2020
Unable to disconnect from the debugger
Hi there, I have just updated to the latest Chrome version 83.0.4103.61 and now not able to disconnect from the debugger.
The error in the console is as below,
(node:3408) UnhandledPromiseRejectionWarning: TractorError: Protractor already running.
(node:3408) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 2)
(node:3408) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
Jeff Judkins
May 21, 2020
Multiple Tabs
Hi! I've been using this extension for years. Just recently, it started malfunctioning and I don't think it is something on my end. But it always could be. Anyway, when I have the extension set to "auto", it opens tab after tab, infinitely. The only way for me to stop the tabs from being opened is to shut down the node process. For now I have it set on "manual"
Paul Cormier
Dec 21, 2019
Dec 19th Update: Lost all code syntax coloring in Debug Window
Since the update, the NiM debug window has no code syntax coloring. All text is the same (grey) color. My regular Chrome Debugger Window continues to color-code as before.
Bret Hansen
Jul 8, 2019
NiM no longer detects node --inspect on port 9229
I have used NiM for > 1 year. It just quit working. I am using Chrome 75.0.3770.100. I can navigate to chrome://inspect/#devices and attach to the node --inspect. However, NiM set to localhost and port 9229 fails to notice automatically and manual fails as well.
NiM shows it is version 2.2.1. I am on a Mac.
Viktoria Khaslarova
Sep 19, 2018
Compatibility with latest chrome
After updating the Chrome to the Version 69.0.3497.92 , breakpoints doesn't work in dev-tools untill the property v8only=true is removed
Jimmy Cyberdeck
Aug 10, 2018
port problem
port 9229 not inuse
Jorge Molero
May 9, 2018
Sourcemaps not working
Thanks for this extension, it is great.
However, it doesn't let sourcemaps work. I can set breakpoint in my original .ts file but it doesn't stop there.
They work if opening the devtools from chrome://inspect
Any idea how to fix that?
Thanks!
Aleksandr Pezikov
Nov 16, 2017
launch error
On icon click it disappear in panel and extention deactivates