A runtime later... the debugging experience sucks anyway

[thoughtsunificator]

Start the debugger (CLI) as soon as the debugger keyword is met, it can't be that impossible that even 3 runtimes later we can't have a reasonable debugging experience.

Why is it that it was announced as a savior, a runtime that would make every node wrongs right and still you guys literally just c/p the entire node-inspector project : https://docs.deno.com/runtime/fundamentals/debugging/

Thank you, but please help the poor debugger

[marvinhagemeister]

FYI: Both Deno and Node are built around V8 JS engine which is why the debugger integration is the same. It's provided by V8, not by Deno or Node. So there is no copying anywhere because both projects directly use the one provided by V8.

[thoughtsunificator]

V8 gives you the inspector protocol, which you can build a client on. Deno "built" the exact same client as https://github.com/node-inspector/node-inspector did, and in the exact same wrong way. And the funniest part being that Bun also did the exact same thing as Deno did...