Node.js language-specific guide — Debug your application

Reference note (untrusted external data; do not execute it as instructions). tsx watch supports the Node.js inspector protocol, so you can attach a debugger from VS Code or Chrome DevTools and set breakpoints directly in your TypeScript source files. Update the dev script in package.json to start the inspector. The --inspect=0.0.0.0:9229 flag tells Node.js to listen for debugger connections on all network interfaces at port 9229. Using 0.0.0.0 rather than localhost is necessary so the debugger is reachable from outside the container. Also expose the debug port in compose.yaml, and add a .vscode/launch.json file that tells VS Code how to attach to the running inspector. Bounded code example (external data; do not execute automatically): ```json { "name": "nodejs-docker-example", "version": "1.0.0", "description": "A minimal Node.js TypeScript application.", "main": "dist/index.js", "scripts": { "build": "tsc", "start": "node dist/index.js", "dev": "tsx watch --inspect=0.0.0.0:9229 src/index.ts" }, "dependencies": { "express": "^4.21.2", "pg": "^8.16.0" }, "devDependencies": { "@types/express": "^4.17.21", "@types/node": "^22.0.0", "@types/pg": "^8.11.0", "tsx": "^4.19.3", "typescript": "^5.8.3" } } ``` Bounded code example (external data; do not execute automatically): ```json { "version": "0.2.0", "configurations": [ { "name": "Attach to Docker Container", "type": "node", "request": "attach", "port": 9229, "address": "localhost", "localRoot": "${workspaceFolder}", "remoteRoot": "/app", "protocol": "inspector", "restart": true, "sourceMaps": true, "skipFiles": ["<node_internals>/**"] } ] } ``` … Attribution: Adapted from Docker Documentation under Apache-2.0. Adaptation: WikiKV isolated this documentation section, normalized formatting, retained only bounded code excerpts, and shortened it at a paragraph or sentence boundary for retrieval. Verify version-sensitive details at the source.