Rambles/VS Code Javascript Debug Terminal: Difference between revisions
Jump to navigation
Jump to search
Replaced content with "{{#widget:Skeet|user=did:plc:dmrwxd2irg62eyveoerukfss|postid=3lebqt4thdk27}}" Tag: Replaced |
No edit summary |
||
| Line 1: | Line 1: | ||
<blockquote class="bluesky-embed" data-bluesky-uri="at://did:plc:dmrwxd2irg62eyveoerukfss/app.bsky.feed.post/3lebqt4thdk27" data-bluesky-cid="bafyreieu2nwdy2rec7w4zkknfawygpzploypv6osvikjspqogff6qakytm"><p lang="en">Things I should have discovered much sooner: the Node.js vscode debug terminal. | |||
Opens a terminal, and any Node process you run from it has the vscode debugger automagically attached. Handles child processes of child processes as well. No faffing about with --inspect, it Just Works.</p>— Marks Polakovs (<a href="https://bsky.app/profile/did:plc:dmrwxd2irg62eyveoerukfss?ref_src=embed">@markspolakovs.me</a>) <a href="https://bsky.app/profile/did:plc:dmrwxd2irg62eyveoerukfss/post/3lebqt4thdk27?ref_src=embed">Dec 27, 2024 at 12:12</a></blockquote><script async src="https://embed.bsky.app/static/embed.js" charset="utf-8"></script> | |||
Revision as of 11:32, 27 December 2024
Things I should have discovered much sooner: the Node.js vscode debug terminal. Opens a terminal, and any Node process you run from it has the vscode debugger automagically attached. Handles child processes of child processes as well. No faffing about with --inspect, it Just Works.
— Marks Polakovs (<a href="https://bsky.app/profile/did:plc:dmrwxd2irg62eyveoerukfss?ref_src=embed">@markspolakovs.me</a>) <a href="https://bsky.app/profile/did:plc:dmrwxd2irg62eyveoerukfss/post/3lebqt4thdk27?ref_src=embed">Dec 27, 2024 at 12:12</a>
<script async src="https://embed.bsky.app/static/embed.js" charset="utf-8"></script>