Feature request: ability to enable/disable node.js instances in dedicated devtools

25 views
Skip to first unread message

Juan Campa

unread,
Aug 14, 2017, 1:50:16 AM8/14/17
to Google Chrome Developer Tools
FEATURE
Add ability to enable/disable node.js instances in the "Sources" panel (see screenshot). This will remove all sources from the CMD+P search and disable all breakpoints (disconnect to the target process?)


REASONING
The Node.js dedicated window shows all running targets it detects and allows you to debug them simultaneously. This is great but it can get very confusing when trying to navigate files and set breakpoints: some files are duplicated if they are included in more than one node.js instance. This is a common problem when you share code across services.



david...@holidayextras.com

unread,
Sep 5, 2017, 6:28:07 AM9/5/17
to Google Chrome Developer Tools
The other thing which is confusing, shown in Juan's screenshot, is the inability to name or otherwise easily distinguish multiple running node threads. 
Especially in the context chooser in the console panel.
Reply all
Reply to author
Forward
0 new messages