Reviews & Comments of Node.js V8 --inspector Manager (NiM) chrome extension

From November 29th, 2016 to February 3rd, 2023, 77% user give 5-star rating, 9% user give 4-star rating, 5% user give 3-star rating, 2% user give 2-star rating, 7% user give 1-star rating. for Node.js V8 --inspector Manager (NiM) chrome extension.

Reviews of node.js v8 --inspector manager (nim):


Clifton Collins February 3rd, 2023
Clifton Collins

Wow. The easiest way to get debugging started. I Love how the folder is already selected when the debugger automatically launches with the node app browser.


A B September 28th, 2021
A B

Very cool extension. Prefer it over paid solutions and suggest it to co-workers :) Thanks you, Folks!


Taoh Green March 27th, 2021
Taoh Green

Can't work without it. Amazing!


Johnny George August 2nd, 2020
Johnny George

Hey there! Brand new user, but I just wanted to say thank you for this! I've been searching for months for a solution to my chrome debugger not working anymore and stumbled upon a github thread where someone posted this extension as a possible fix, and lo and behold it is! Again, thank you so much for putting this out here!


Prakash Gp July 16th, 2020
Prakash Gp

Is there any way i can debug network requests ??


Michael Quad April 2nd, 2020
Michael Quad

a peice of art, that's it


Sebastien Lapratte January 9th, 2020
Sebastien Lapratte

Very usefull! Thanks for you great work!


Owen Luke December 26th, 2019
Owen Luke

Great job!


aaliyah December 26th, 2019
aaliyah

Very useful extension!


Suneil Nyamathi December 20th, 2019
Suneil Nyamathi

I keep getting notifications from this plugin even though I've opted out in the settings.


John Magdy ([BR]John_Magdy) October 29th, 2019
John Magdy ([BR]John_Magdy)

Good one but it makes me crazy when it duplicated that `Node.JS DevTools` Tab more than 40 times in minute... please do something in that :( and please can anyone explain why do it need `Viewing my Email Address` Permission ??? (i couldn't find any reason for that... on my opinion at least)


Денис Авілов April 8th, 2019
Денис Авілов

Such a useful extension which gets you rid of annoying routine actions each time you run a nodejs script.


Hector Bas December 8th, 2018
Hector Bas

I just got to say, such a simple add-on that is gonna resolve SOOO many headaches. Luckily for me I am at the beginning of the road in setting up a new scripting environment with ClearScript. My whole reasoning for using this engine was 1) we are .NET developers & 2) the support of Google's scripting engine, V8. When it comes to javascript and debugging, Google's dev tools are just unparalleled. Easy to use AND we don't have to use a custom debugging tool for that one off project. Naturally, as I am investigating this new tool, I came across the ability to attach CDT as a debugger, but the process to get it attached was slightly tedious. One of the first solutions I cam across was this chrome extension. Initially I ignored it, since it was clearly advertised for Node.js. However I wanted to see what kind of options could be specified, and man was it easy to configure it for my use case. The only "special" thing I really had to do was change the DevTools url/version in options to point to: "chrome-devtools://devtools/bundled/inspector.html". Afterwards, it worked flawlessly. A few things I would recommend to the extension developer: 1) I'd highly recommend stating somewhere clearly in the description for support of other such tools such as ClearScript, I almost skipped out on this gold mine 2) Potential support for specifying multiple host and port profiles with a naming scheme and active Boolean flag? 3) An option to auto-launch the debugger for an X amount of time from the point of enabling OR if now launch after X time then auto-disable untill manually re-enabled. This would be to prevent unintended attachments (scenario for multiple developers who work on the same set of remote servers) and just have a smooth debugging experience for the time allotted. Perhaps change the color of the logo in the quick launch bar to indicate that it is not actively monitoring. 4) Would it be possible for you to tell CDT to automatically pause execution upon load? If not, not a huge big deal as it seems most of these engines have flags for this type of scenario to make sure that you don't miss any script execution. Overall, fantastic job!


Gregg Tavares September 20th, 2018
Gregg Tavares

There is no defensible reason to have to provide an email address. node does not require an email address, chrome does not require an email address, clang does not require an email address.


Fernando Catacora August 20th, 2018
Fernando Catacora

Man, this tool is super useful, thanks!!


Fatih Kaya June 20th, 2018
Fatih Kaya

Thank you for this awesome extension. It helped me a lot.


Giovanni Viola April 15th, 2018
Giovanni Viola

Great! Easy and powerful debug


Joshua Newton April 5th, 2018
Joshua Newton

OMG. Where has this been my entire life. Literally closing the devtools tab over and over to watch it magically re-open. No more manually copying debug urls out of my docker logs!!!!


Fabio Spampinato March 23rd, 2018
Fabio Spampinato

This is one of those things you wish you knew about 2 years ago, greatly recommended!


Alan Clelland February 5th, 2018
Alan Clelland

Works ok but I need to manually enter the server IP every time. If I set the IP to, for example, 1.1.1.1 and then click "launch dev tools" a new Tab will open but the ws= parameter will be set to the remote servers local network IP (ie, 192.168.1.1.) rather than the one I told NiM to use.


Allan Dy January 26th, 2018
Allan Dy

Love it but I cannot seem to turn off the make tab active option. Its off but still decides to set focus while Im using nodemon.


Jeet October 10th, 2017
Jeet

Even after specifying ip address and port where NodeJS app is hosted, this plugin is unable to inspect the app. Anything else I need to take care of?


sydcanem October 4th, 2017
sydcanem

Suddenly consumes 90% of my CPU on Mac. It's a great extension but I can't say if it's safe to use.


MJ Abadilla September 25th, 2017
MJ Abadilla

This will definitely save us time. Thank you!


Jakob Anderson September 1st, 2017
Jakob Anderson

This fixed a frustrating painpoint for my node dev workflow. So grateful.


Niall O'Callaghan July 8th, 2017
Niall O'Callaghan

Amazing.


Michael Richardson May 17th, 2017
Michael Richardson

LOVE this extension though I think it's life will be short lived. As of Chrome Version 60.0.3102.0-canary, you can visit chrome://inspect and click "Open dedicated DevTools for Node" and you'll get devtools, FULLY connected as a debugger (can profile startups, inspect objects, console works perfectly, etc..) that will reconnect to the same debugger port (no more copy/paste UID issues) AND can even have multiple "connections" (different debugger port presets so you can easily switch between multiple apps). Now if we can JUST get an extension that opens this thing directly (no more chrome://inspect), we're all set!


Daniel McQuiston May 9th, 2017
Daniel McQuiston

This is really helpful for me. I use it with nodemon. My only gripe with it and the reason why I give 4 stars instead of 5 is that the way dev tools gets invoked, it always steals focus. I have to disable this plugin when I don't need it or change my watch script to not at "--inspect". If the author can't change the way focus is stolen, they should add an quick on/off toggle to its icon. Definitely a very useful plugin and I recommend it highly to any other Node.js developers.


Qimin Sun May 1st, 2017
Qimin Sun

It's useful for our poor nodejs programmers.


Michael Richardson April 27th, 2017
Michael Richardson

Now that it's working as I think most of us wanted (automatic, restarts, etc), this is worth cash (seriously dev, where can I contribute?). MUST have for node developers!


Adrian Moisă March 25th, 2017
Adrian Moisă

Nice to have the auto-open feature.


Alexander Mills March 10th, 2017
Alexander Mills

Works really well, I have a bash script that runs "node --inspect --debug-brk bin/www.js", and the extension gets invoked everytime, and restarts the debugging session for me. Really nice, thanks!


Colin Richardson February 16th, 2017
Colin Richardson

Had some problems with it at first opening 2 windows and not breaking properly. But now it seems to be working perfectly and completely as expected. Don't forget to use --inspect-brk for people writing synchronous code.


Prayash Thapa February 17th, 2017
Prayash Thapa

So convenient! ?


JDG February 2nd, 2017
JDG

Excellent! Thank you _very_ much!


Marco Arduini January 27th, 2017
Marco Arduini

Brilliant! Great job. Extremely useful.


Simon Mawdsley January 26th, 2017
Simon Mawdsley

yay it works! much happiness, many thanks


Miguel San Segundo January 6th, 2017
Miguel San Segundo

Great work! Works perfect. It's well designed and it has great support.


Randall Ma January 6th, 2017
Randall Ma

u already kno what it is, its ya boy desiigner hype man extraordinaire and this chrome extension works really good 10000/10


667 December 16th, 2016
667

To be fair... I'm biased as I wrote it. But also being self critical and always open to constructive criticism, I feel alright with saying that I'm pleased with the result so far. It works as intended and solves the initial problem which it was intended to solve. So thumbs up to the developer. But please continue improving as is required. ;)


Justin Collum December 15th, 2016
Justin Collum

Really nifty little tool


adrian wardell November 16th, 2016
adrian wardell

Great extension. It does exactly what it claims and certainly did simplify my workflow. Adopting NIM, I've been able to return to my old tried and true workflow, while using the new integrated Node V8 Inspector. Thanks.


A Google User November 29th, 2016
A Google User

Very nice! I hate cutting/pasting URLs over and over and this seems to solve this entirely. Thank you for doing it.