Debugging Babel and Node done right
Requirement: - Excellent feedback during development - Debugging with source maps Method: I'm using these scripts in package.json. "scripts": { "di": "node-inspector -d=7000 -p=8000 --save-live-edit --hidden node_modules/", "ds1": "babel ./server -d ./build/server -s -w", "ds2": "nodemon --watch ./build/server --delay 100ms --debug=7000 ./build/server/main.js" }, Then run "npm run ds1; npm run ds2; npm run di" Why: I took some time to put this together, after navigating all the tools out there. I personally find this to be "correct". Thought I'd…
Debugging Babel and Node done right launched on July 2, 2016 with 22 votes, #1,516 of 3,671 launches that month and more than 75% of that year's launches.
In plain words
This is a development workflow setup for debugging Node.js applications written in Babel. It combines three npm scripts that work together: one transpiles Babel code to a build directory with source maps, another watches the build directory and restarts the server with debugging enabled, and the third launches node-inspector for interactive debugging. The setup is designed for developers who need reliable feedback and accurate source mapping during development.
written from the facts on this page · September 2026
From the sources
In the maker’s words, at launch
Requirement: - Excellent feedback during development - Debugging with source maps Method: I'm using these scripts in package.json. "scripts": { "di": "node-inspector -d=7000 -p=8000 --save-live-edit --hidden node_modules/", "ds1": "babel ./server -d ./build/server -s -w", "ds2": "nodemon --watch…
Does a similar job
all alternatives →
Nub – A Bun-like all-in-one toolkit for Node.jsJun 2026 · github.com · ▲277Colin here, creator of Nub. I’ve had the general shape of this in mind for years. Nub runs your code with stock `node`, augmented with a `--require` preload hook[0] that adds a transpiler (oxc-powered, packaged as a Node-API add-on), registers a module resolution hook[1], and injects polyfills as needed for APIs like `Worker`, `Temporal`, etc. All purely additive, your code ultimately runs using Node’s actual engine & stdlib implementations. [0] https://nodejs.org/api/cli.html#-require-module [1]…
Letting LLMs Run a Debugger2025 · github.com · ▲147Hey HN, I just built an experimental VSCode extension called LLM Debugger. It’s a proof-of-concept that lets a large language model take charge of debugging. Instead of only looking at the static code, the LLM also gets to see the live runtime state—actual variable values, function calls, branch decisions, and more. The idea is to give it enough context to help diagnose issues faster and even generate synthetic data from running programs. Here’s what it does: * Active Debugging: It integrates with Node.js debug sessions to gather runtime info (like variable states and stack traces). *…
I've been making JavaScript sandbox alone for 6 years2022 · playcode.io · ▲397Hi HN! Thanks for your attention to my post. It was a big challenge to run most of Node.js packages in browser, fast moreover. Virtual File system, resolve import/export. I got cold many times, depressions, burned out, yet still alive and finished it. Many guys helped me with an advice. Many users give a lot of positive feedback. There are 200,000 monthly unique users. I work full time now because of the freemium business model. To be honest - I am happy after many years of hard work.
Let Claude Code control Node.js debugger2025 · github.com · ▲9Debugging is hard for LLMs, because they primarily depend on source code, and they don't have access to runtime state. I spent countless hours debugging code, and the only way I found LLMs useful for that, is to ask them to add log lines. That's annoying, because it pollutes my code and adds unnecessary diffs. So we made an MCP server that solve this problem. It gives MCP clients (like Claude Code) access to a NodeJS inspector, so they can: 1. set breakpoints 2. step in, step out, continue 3. fetch the current execution location 4. read console output 5. run JS using eval To try: 1. run a…
- WMWe made an MCP server so Cursor can debug Node.js on its own2025 · npmjs.com · ▲139
6to5 – Turn ES6 code into vanilla ES5 with source maps and no runtime2014 · github.com · ▲48🐠 Babel is a compiler for writing next generation JavaScript. - babel/babel
More dev tools this month
the category →

open-source IDE for thoughtful software design. Contribute to devdotfast/whiteboard development by creating an account on GitHub.
Dev tools · 27d ago · github.com

Contribute to reladraw/reladraw development by creating an account on GitHub.
Dev tools · 25d ago · github.com
OpenBot▲362Grok Bot alternative: free, local, open-source, multiplayer
Dev tools · 22d ago · openbot.run
Talanoa▲341Hi HN, I’m a fullstack developer, and honestly, I’ve lost count of how many side projects I’ve worked on over the years. But one idea kept coming back to me: a different kind of email client. It first came to me in 2014: “What if we could handle emails more like conversations?” Every year, I’d revisit this concept in my “Build Notes.” Ten years later, no one had built exactly what I had in mind — so I finally decided to do it myself. That’s how Talanoa was born. I wanted something focused on people, not timelines. I was tired of marking messages as unread just to remember to reply later, or…
Dev tools · 20d ago · talanoa.email
CoreSpeed▲332One MCP for everything your agents need: apps, memory, tools
Dev tools · 27d ago · corespeed.io
Source: Show HN post ↗ · launch text quoted in part
Launched alongside, July 2016
the whole month →
Web Design in 4 minutes▲1,624Learn the basics of web design in 4 minutes with this interactive tutorial.
Life & fun · 2016 · jgthms.com




