command-line flag to launch an instance/window of the "dedicated DevTools for Node"
Reported by
raina...@gmail.com,
May 17 2017
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3100.0 Safari/537.36 Steps to reproduce the problem: 1. Search http://peter.sh/experiments/chromium-command-line-switches/ for related flags 2. Find none 3. What is the expected behavior? Something like --node-dev-tools as a flag to chrome.exe What went wrong? I wanted to launch the devtools node debugger directly rather than having to browse to "chrome://inspect" and then click "Open dedicated DevTools for Node" Did this work before? N/A Chrome version: 60.0.3102.0 Channel: canary OS Version: 10.0 Flash Version: Shockwave Flash 26.0 r0
,
May 17 2017
Primary feature request seems to be triggering the window from the command line. Dgozman, wdyt?
,
Oct 4 2017
,
Dec 11 2017
WontFix due to lack of priority / resources |
||||
►
Sign in to add a comment |
||||
Comment 1 by jonathan...@gmail.com
, May 17 2017Labels: -OS-Windows -Type-Bug -Pri-2 OS-All Pri-3 Type-Feature
Owner: pfeldman@chromium.org
Status: Untriaged (was: Unconfirmed)