New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 642577 link

Starred by 4 users

Issue metadata

Status: WontFix
Owner:
Closed: Oct 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 2
Type: Bug



Sign in to add a comment

DevTools: better URL for debugging node

Project Member Reported by paulir...@chromium.org, Aug 31 2016

Issue description

I've caught a few people copypasting the debug link a few times, thinking that it's changing.

Based on a conversation with Pavel we think it can be simplified a bit:

    chrome://inspect/node:9227

From there we'll connect, get the version, and fetch the right frontend. We've done the same thing for remote debugging a few times.

Eugene, pavel said you might have already been thinking along these lines?
 
Can I close this or do you think we still need it, now that we have the "checkbox"?
Cc: eostroukhov@chromium.org
Owner: pfeldman@chromium.org
Pavel's gonna take this.

We are thinking it will look something like...

▸ node --inspect --debug-brk server.js
Debugger listening on port 9229.
Warning: This is an experimental feature and could change at any time.
To start debugging, open the following URL in Chrome:
    chrome-devtools://inspect?localhost:9227

And the URL would then not change significantly after opening it.

Comment 3 by atif...@gmail.com, Oct 31 2016

Hey guys, thanks for raising this. Is it possible to also launch the browser like node-inspector does?
Status: WontFix (was: Assigned)
No plans to proceed here.

Sign in to add a comment