Node.js V8 Inspector

Node.js V8 Inspector

Extension for launching V8 Inspector for Node.js debugging

Node.js V8 Inspector promo image
What is Node.js V8 Inspector?

Node.js V8 Inspector is a Chrome extension by Continuation Labs. This extension has 2,000 weekly active users, an average user rating of 3.78, and was removed from Chrome Web Store 9 months ago. The latest version, 0.12.0, was updated 6 years ago.

Stats
This extension was removed from Chrome Web Store on 2022-06-29
Stats date:
Users: 2,000
Rating: 3.78 (18)
Version: 0.12.0 (Last updated: 2017-02-07)
Creation date: 2017-02-07
Manifest version: 2
Permissions:
  • http://*/
  • storage
  • notifications
Size: 40.55K
Email: Click to see
URLs: Website
Risk impact: Moderate risk impact
Risk likelihood: High risk likelihood
Found a bug?

Other platforms

Not available on Firefox
Not available on Edge
Summary
Node.js V8 Inspector is a Chrome extension for attaching DevTools to running Node.js applications (requires Node v6.3.0). After installing this extension, debug your application using the following steps:

1. Run a Node.js application with the --inspect command line flag.
2. Open the node-v8-inspector extension in Chrome.
3. Verify that host and port match your application's host and debug port. The default value is 9229, the same default used by Node.js. The host defaults to localhost.
4. Press Launch V8 Inspector button.
5. Debug your application.
6. Profit (optional).

Source code at 
https://github.com/continuationlabs/node-v8-inspector
Safety
Risk impact

Node.js V8 Inspector requires some risky permissions and may not be safe to use. Exercise caution when installing this extension. Review carefully before installing.

Risk impact measures the level of extra permissions an extension has access to. A low risk impact extension cannot do much harms, whereas a high risk impact extension can do a lot of damage like stealing your password, bypass your security settings, and access your personal data. High risk impact extensions are not necessarily malicious. However, if they do turn malicious, they can be very harmful.

Risk likelihood

Node.js V8 Inspector may not be trust-worthy. Avoid installing if possible unless you really trust this publisher.

Risk likelihood measures the probability that a Chrome extension may turn malicious. This is determined by the publisher and the Chrome extension reputation on Chrome Web Store, the amount of time the Chrome extension has been around, and other signals about the Chrome extension. Our algorithms are not perfect, and are subject to change as we discover new ways to detect malicious extensions. We recommend that you always exercise caution when installing a Chrome extension, especially ones with higher risk impact and/or higher risk likelihood.

Subscribe to the premium plan to see more risk analysis details
User reviews
Thanks for the extension! Very helpful for node.js developers!
by Edward Diehl Edward Diehl, 2017-06-17

I'm recently coming to understand that Node 6.x and 7.x use very different debuggers and some combination of the older debugger, chrome and devtools are such that things are largely broken if you try to use this with Node 6.x (LTS). I think that's why my experience with this was poor. I have not tried with Node 7.x though.
by Michael Richardson Michael Richardson, 2017-05-17

Have no file tree if open inspector through the extension.
by Ilia Baryshnikov Ilia Baryshnikov, 2016-11-10
View all user reviews
Promo images
Node.js V8 Inspector small promo image
Small promo image
Similar extensions

Here are some Chrome extensions that are similar to Node.js V8 Inspector:

Node Debugger Node Debugger
Publisher: Apt-2531
User count: 1,000
Rating: 3
Debug Node in Chrome devtools
Node.JS is the Only Real Dev Language Node.JS is the Only Real Dev Language
Publisher: Jackson Fall
User count: 108
Rating: 1
Replaces the text 'Node.JS' with 'The Only Real Dev Language'.
Node.js V8 --inspector Manager (NiM) Node.js V8 --inspector Manager (NiM)
User count: 20,000
Rating: 93
Manages DevTools with Node V8 Inspector (node --inspect) Debugging Workflow