Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Node --inspect uuid #11701

Closed
rumkin opened this issue Mar 5, 2017 · 2 comments
Closed

Node --inspect uuid #11701

rumkin opened this issue Mar 5, 2017 · 2 comments
Labels
duplicate Issues and PRs that are duplicates of other issues or PRs. inspector Issues and PRs related to the V8 inspector protocol

Comments

@rumkin
Copy link
Contributor

rumkin commented Mar 5, 2017

Currently chrome inspector creates unique session id to access from chrome:

chrome-devtools://devtools/bundled/inspector.html?experiments=true&v8only=true&ws=127.0.0.1:9229/5425c0e5-e0e1-433e-b194-ec4b4461f57a

When I try to run it automatically on remote host I could not parse it's output to extract this uuid. So it would be preferable to determine access token (instead of uuid) myself.

@mscdex mscdex added duplicate Issues and PRs that are duplicates of other issues or PRs. inspector Issues and PRs related to the V8 inspector protocol labels Mar 5, 2017
@mscdex
Copy link
Contributor

mscdex commented Mar 5, 2017

I think is mostly a duplicate of #11496. If you still specifically want/need just the uuid, please add your request to that issue.

@rumkin
Copy link
Contributor Author

rumkin commented Apr 30, 2017

@mscdex It's not a duplicate of 11496 which is about internal node API and this issue is about CLI.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate Issues and PRs that are duplicates of other issues or PRs. inspector Issues and PRs related to the V8 inspector protocol
Projects
None yet
Development

No branches or pull requests

2 participants