I have noticed that since the latest update of Chrome V76 the extension is not opening up a new tab automatically for the devtools and looks like it's not picking up the WS as per the screenshot? The work around I have had to do is start the debugger and then open up chrome://inspect then click on the inspect link to open the devtools for that WS.

Dude, I love this extension, many thanks!

Small niggle, I have a couple of services running at the same time and I find that I often need to switch between them... would it be difficult to have NIM listen for multiple ports, and open devtools for each?

The deluxe version of this feature would be to have a user configured list of ports, each with a toggle and a manual button...

Food for thought... thanks again :)

Thanks a lot for such useful tool!

Unfortunately at some point the extension started crashing on my machine when i click on it (Ubuntu 16.04, Chrome 59). Maybe you have any idea where is the source of this issue?

I have an issue where restarting my server through Nodemon does not close the tab, but instead renders this error message:

After looking through the source code I think I've isolated the problem to here. The catch for the HTTP request does not consider a valid case where the debug server is not down, but the ID of the debugger websocket changes.

A proposed solution would be to store the unique identifier for each devtools session, and check if that identifier is in the returned JSON from the localhost debug server. Requests coulda also be minimized by making the request only once and filtering $scope.devToolsSessions according to the returned identifiers.

I'd be willing to PR this in the next couple days with your OK @june07

Edit: Initial conversation about this issue can be found here.

NiM extension is beautiful, but after a year of rest, I launched it again on a new project and discovered two problems.

• extension not saves auto/handler tubler (my tumbler even a little buggy and glitch, i can record gif, seem to be low-fps gpu)
• chrome inspector not saves console options

MacOs 10.14.6 Mojave, Chrome 80.0.3987.132

When using the plug-in, sourcemaps for babel aren't been mapped to the source. This is similar in symptom to NodeJS issue #8369 -- however, when I access the dev tools using chrome://inspect the issue is not seen.

Love this plug-in and would be happy to help however is needed-- I can perform more info as needed and would be willing to take a crack at opening a PR if I could get some direction.

Thanks.

I am getting a weird macOS (11.3.1) system notification when I try to use the NiM keyboard shortcut, option-I — see the attached screenshot, it's just Chrome telling me that NiM owns the shortcut, but nothing happens. (In other words, I type the shortcut and get the notification telling me NiM owns it, but DevTools doesn't open.)

Any thoughts?

I'm running Chrome 90.0.4430.93 (Official Build) (x86_64), NiM 2.8.0, and macOS 11.3.1 (20E241).

problem remains also after uninstall and reinstall of the extension Workaround: in chrome developer console goto Application, right click on local storage and clear.

Uncaught (in promise) TypeError: Cannot assign to read only property 'length' of object '#' at SettingsStorage.setPreference [as _setCallback] (host.js:106) at SettingsStorage.set (common.js:330) at VersionController._migrateSettingsFromLocalStorage (common.js:429) at VersionController._updateVersionFrom11To12 (common.js:396) at VersionController.updateVersion (common.js:366) at MainImpl._createSettings (main.js:37) at MainImpl._gotPreferences (main.js:34) at InspectorFrontendHostStub.getPreferences (host.js:105) at MainImpl._loaded (main.js:32)

Hello I'm currently integrating V8Inspector in my company application that already embeds V8. I'm currently facing the issue your plugin NIM has already solved for Node : how to simplify the start of a debug session ? Do you think it's possible to use NIM to automate the launching of CDT in my application? Thanks and regards Aligre

Environment

OS X 10.12.6 (16G29) Chrome 60.0.3112.90 (Official Build) (64-bit) NiM 0.13.8

What happened?

After installing NiM, I was working in Google Docs and attempted to use cmd+i to italicize some text but nothing happened. Disabling NiM, cmd+i worked again. Inspecting manifest.json, I noticed that cmd+i was registered as the open devtools keyboard shortcut when it should be cmd+option+i (View -> Developer -> Developer Tools ⌥⌘I).

What did you expect to happen?

I did not expect NiM to intercept keyboard shortcuts.

Thank you for NiM, for the reasons you outline in your blog post it's a real time saver. 🍻

It turns out NiM doesn't work without an active internet connection because it tries to connect to http://chrome-devtools-frontend.june07.com/.

Why does NiM need that while chrome://inspect/#devices perfectly works without it?

More importantly, how can we configure NiM to work without an internet connection?

The "Make Window Focused." option does not fit my workflow, so I disable it. However, it is useful to be notified when debugger pauses (at a breakpoint or when an exception is caught).

It would be helpful to have a "Make Window Focused On Debugger Pause" option.

Hi,

I'm getting an error on startup; this is what I'm doing.

I configure the host to be "auto" in NiM:

I create a simple main.js file, and then I run it using node --inspect-brk main.js. NiM detects the URL and opens, but I get the following error:

OS & Versions: OS: Manjaro Linux Node: v14.4.0 NiM: 2.4.2 (as seen by the first screenshot)

Thank you