Skip to content
This repository has been archived by the owner on Feb 1, 2022. It is now read-only.

Freeze UUID token in chrome devtools link #45

Closed
darky opened this issue Apr 20, 2017 · 7 comments
Closed

Freeze UUID token in chrome devtools link #45

darky opened this issue Apr 20, 2017 · 7 comments

Comments

@darky
Copy link

darky commented Apr 20, 2017

During developing process very uncomfortable open chrome devtools again and again by new generated link. I want to pass like: --inspect-token=00000000-0000-0000-0000-000000000000 or better: --inspect-token=developing and already have the same link, that allow me simple refresh browser tab, when node process will restarted

@ofrobots
Copy link
Contributor

ofrobots commented Apr 20, 2017

Chrome 57+ comes with a dedicated DevTools for Node.js that gets rid of the need to copy/paste the URL across restarts:

image

You can access this from chrome://inspect. Can you give this a shot and see if this addresses your use-case?

@darky
Copy link
Author

darky commented Apr 20, 2017

@ofrobots, it not resolved this problem. When node.js process restarted, need to click again on inspect link and open new window with actual process. Old window not working after restart.

@ofrobots
Copy link
Contributor

For me it does seem to work after a restart. @eugeneo: does this behaviour make sense to you?

@darky
Copy link
Author

darky commented Apr 20, 2017

@ofrobots, I don't understand how it works for you, it not logical due to this behaviour

When node.js process restarted, need to click again on inspect link and open new window with actual process. Old window not working after restart.

Also, I think, that this token need for security reasons, but, if chrome://inspect can simply find attached process, why it need?..

@jkrems
Copy link
Collaborator

jkrems commented Apr 20, 2017

@darky To clarify: There's two links. @ofrobots was talking about this one if I understand him correctly:

screen shot 2017-04-20 at 8 31 09 am

If you're using the default port for --inspect, that link should work and keep working without any re-opening of the DevTools.

@jkrems
Copy link
Collaborator

jkrems commented Apr 20, 2017

I'm afraid this issue isn't actually about node-inspect (the command line debugger) but about the v8 inspector integration itself (node --inspect). Sorry for the confusion.

There are already issues in nodejs/node:

Feel free to open a new issue in nodejs/node for this feature request! :)

@jkrems jkrems closed this as completed Apr 20, 2017
@darky
Copy link
Author

darky commented Apr 20, 2017

@jkrems, thanks for the answer

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants