Describe preferred way to start Chrome DevTools (#1562)

Chrome DevTools have been shipping an option to open a "dedicated" Node frontend for a long time. That frontend has several Node-specific enhancements, including being able to reattach to a Node instance that was restarted.
nodejs · Feb 3, 2018 · a975e20 · a975e20
1 parent 49aef82
commit a975e20
Show file tree

Hide file tree

Showing 2 changed files with 335 additions and 206 deletions.
diff --git a/locale/en/docs/inspector.md b/locale/en/docs/inspector.md
@@ -27,11 +27,10 @@ These commercial and open source tools make debugging Node.js apps easier.
 * Can also be installed independently with `npm install -g node-inspect`
   and invoked with `node-inspect myscript.js`.
 
-### [Chrome DevTools](https://github.com/ChromeDevTools/devtools-frontend) 55+
+### [Chrome DevTools](https://github.com/ChromeDevTools/devtools-frontend)
 
 * **Option 1**: Open `chrome://inspect` in a Chromium-based
-  browser. Click the Configure button and ensure your target host and port
-  are listed. Then select your Node.js app from the list.
+  browser. Click the "Open dedicated DevTools for Node" link.
 * **Option 2**: Install the Chrome Extension NIM (Node Inspector Manager):
   https://chrome.google.com/webstore/detail/nim-node-inspector-manage/gnhhdgbaldcilmgcpfddgdbkhjohddkj