Version: v6.9.2
Platform: Windows 10 x64
When you do "node --inspect", it leads you to believe you should be debugging it through the URL it provides. I used it for a while, but it just buggy in general and doesn't work as well as a normal developer tools window. Luckily I discovered that I could do the same stuff but better with chrome://inspect. It would have saved me a lot of time if I found out about it sooner, so I feel that we should at least mention chrome://inspect in addition to the inspector.html URL.
C:\Windows\System32>node --inspect
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://devtools/remote/serve_file/@60cd6e859b9f557d2312f5bf532f6aec5f284980/inspector.html?experiments=true&v8only=true&ws=127.0.0.1:9229/28625829-4e38-4d76-aa23-73cd6a7903e4
>
Maybe it should be more like this:
C:\Windows\System32>node --inspect
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://devtools/remote/serve_file/@60cd6e859b9f557d2312f5bf532f6aec5f284980/inspector.html?experiments=true&v8only=true&ws=127.0.0.1:9229/28625829-4e38-4d76-aa23-73cd6a7903e4
You can also try chrome://inspect
>
Version: v6.9.2
Platform: Windows 10 x64
When you do "node --inspect", it leads you to believe you should be debugging it through the URL it provides. I used it for a while, but it just buggy in general and doesn't work as well as a normal developer tools window. Luckily I discovered that I could do the same stuff but better with chrome://inspect. It would have saved me a lot of time if I found out about it sooner, so I feel that we should at least mention chrome://inspect in addition to the inspector.html URL.
Maybe it should be more like this: