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…
What it does
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 ./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 share. Did not use: babel-watch, babel-node, forever, etc. I found configurations with those tools to not meet the requirements.
Does the same job
all alternatives →- LCLet Claude Code control Node.js debugger2025 · github.com · ▲9
Debugging 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…
- IRIntercept.rest – Faster API debugging2018 · ▲89
Sharing an internal tool that accelerated my development work 10-fold, especially with API debugging. Thought fellow developers here might find it useful. As a developer, I often have trouble reproducing errors at the client end. https://intercept.rest lets me debug and monitor API requests and responses. It is similar to the Network tab in Chrome Developer Tools but works for any API: mobile apps, webhooks, frontend etc. After I shared it with a close circle of friends, they found it incredibly useful and even found new use cases, I never imagined. Been a long time lurker here and…
- AAAt a Glance ESM Support for NPM Packages2022 · ▲9
We've rolled out a feature for openbase.com that we think is a DX game changer for Node devs. Since the emergence of ECMA Script modules, it's been a continuous guessing game as to what kind of exports a package has. That's never really been discoverable without using a site like unpkg, or installing the package and inspecting package.json. Openbase now displays the ES Module support level (e.g. type of exports) on all of their package pages. We added this feature because our devs are some of the folks continually caught off guard by installing an NPM dependency only to find out it's…
More dev tools this month
the category →
Open-source GTM skills for technical founders
Dev tools · 29d ago · gtmcofounder.com
OpenTrailPaper is open-source bike computer firmware for the LilyGO T5S3 4.7" E-Paper PRO. It supports offline maps, GPX routes, FIT recording and Bluetooth sensors.
Dev tools · 1d ago · opentrailpaper.com
Launched alongside, July 2016
the whole month →- WDWeb Design in 4 minutes▲1,624
Life & fun · 2016 · jgthms.com
