Closed
Description
- Version: v7.3.0
- Platform: Ubuntu GNOME 64-bit
- Subsystem: DevTools integration
Previously, I could reload DevTools with a new Node process after restarting, but as of some point between 6.9.2 and 7.3.0, I can no longer reload the page, I'm guessing because the unique Node identifier is no longer there.
Here's two URLs from v6.9.2:
chrome-devtools://devtools/remote/serve_file/@60cd6e859b9f557d2312f5bf532f6aec5f284980/inspector.html?experiments=true&v8only=true&ws=127.0.0.1:9229/b6bb7368-a2ee-4c70-b0e6-e222763651f6
chrome-devtools://devtools/remote/serve_file/@60cd6e859b9f557d2312f5bf532f6aec5f284980/inspector.html?experiments=true&v8only=true&ws=127.0.0.1:9229/539f225c-e4b0-463d-a910-e3ce099c5ac4
Here's two URLs from v7.3.0:
chrome-devtools://devtools/bundled/inspector.html?experiments=true&v8only=true&ws=127.0.0.1:9229/41e80eb3-ebdc-46fc-bed2-dfbc908222c2
chrome-devtools://devtools/bundled/inspector.html?experiments=true&v8only=true&ws=127.0.0.1:9229/2e89f350-7240-4561-9c61-e0f3cf7e2a07
Any chance this could be fixed? It's making step-wise unit test debugging in Node 7 a PITA.
Metadata
Metadata
Assignees
Labels
No labels