You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently debugging with Chromium DevTools is possible but a manual copy paste of the debug socket is needed as you can see from the first screenshot where I copy/pasted "localhost:4000/7u1bqmpvhg" into DevTools. https://github.com/june07/nim is a tool I wrote for Node.js (works for Deno as well) some years back for this and it would be nice to use it for Bun as well, to streamline things.
Node/Deno both implement inspect servers that have a json endpoint which contains data about the debug websocket:
For example, http://localhost:9229/json will display this output which allows local clients to determine the debugger web socket details so as to connect: ws=localhost:9229/abcdbdb5-f00c-4554-88e5-d740ba881234"
Electroid
changed the title
Inspect debug server similar to Node/Deno for easier debugger port/id introspection
Support V8 DevTools protocol
Mar 26, 2024
What is the problem this feature would solve?
Currently debugging with Chromium DevTools is possible but a manual copy paste of the debug socket is needed as you can see from the first screenshot where I copy/pasted "localhost:4000/7u1bqmpvhg" into DevTools. https://github.com/june07/nim is a tool I wrote for Node.js (works for Deno as well) some years back for this and it would be nice to use it for Bun as well, to streamline things.
Node/Deno both implement inspect servers that have a json endpoint which contains data about the debug websocket:
For example, http://localhost:9229/json will display this output which allows local clients to determine the debugger web socket details so as to connect:
ws=localhost:9229/abcdbdb5-f00c-4554-88e5-d740ba881234"
I'm sure those reading this are familar with this in Node... but in case not: https://nodejs.org/en/learn/getting-started/debugging
What is the feature you are proposing to solve the problem?
Implement the same inspector sever /json endpoint
What alternatives have you considered?
No response
The text was updated successfully, but these errors were encountered: