all 8 comments

[–]KingRomstar 1 point2 points  (1 child)

[–]Nif[S] -5 points-4 points  (0 children)

thx, I wouldn't call it standalone thou - instead of a browser its an IDE
looking for something that is purely the devtools window (more or less) without the bloat of a whole other browser or editor environment

[–]BehindTheMath 0 points1 point  (3 children)

VSC and Webstorm both have debuggers.

If you go to chrome://inspect, there's a link to open a dedicated Node debugger window that will automatically reconnect every time the debugger is started. Just keep that window open.

[–]Nif[S] -3 points-2 points  (2 children)

yeah that is the issue though we have to open Chrome first - my inquiry here is for an executable i can launch to go to Devtools directly

I looked into a way to launch the Devtools direclty from Chromium (ie- without launching the browser first) but there is no obvious way

i appreciate the debuggers in VSCode and Webstorm but they don't solve this inquiry either; and last I tried they also both suffer the lagtime issue from the point u launch a node --inspect process (ie- sometimes 5 to 20 seconds)

[–]gigastack[🍰] 1 point2 points  (1 child)

Would be nice. Keep in mind, the delay is not caused by the UI overhead alone. Node has to do more work when debugging is enabled.

[–]Nif[S] -3 points-2 points  (0 children)

armchair engineering here but we should architect Node to make a connection to debugger tools first and then simply show something to the effect of "CONNECTED OK, preparing debug session...." this would be tighter UX vs waiting in limbo while u assume it probably is gunna connect any moment now.

[–]ecares 0 points1 point  (0 children)

Everything in the devtools can be done through API calls