远程调试Node.js时如何加载源码？Docker+VSCode场景求助

Hey Rob, I’ve run into this exact source mapping issue with remote Docker Node.js debugging before—let’s get your local VSCode to see all the remote source code properly. Here’s what you need to do:

1. First, Sync Remote Container Code to Your Local Workspace (Read-Only) #

Since you only need read access, the simplest way is to copy the entire remote app directory to your local VSCode workspace. Run this command in your Windows terminal (make sure Docker Desktop is running and connected to your Linux Docker host):

docker cp <your-container-name-or-ID>:/opt/myApp/. ${workspaceFolder}

This will mirror the remote /opt/myApp directory structure directly into your local workspace. Just avoid editing these local files to keep it read-only.

2. Tweak Your launch.json for Precise Source Mapping #

Your current config is close, but adding sourceMapPathOverrides will help VSCode correctly link remote compiled files (or source maps) to your local copied files. Update your launch config like this:

{
  "type": "node",
  "request": "attach",
  "name": "Attach to Remote QA",
  "port": 9229,
  "address": "11.222.333.444",
  "localRoot": "${workspaceFolder}",
  "remoteRoot": "/opt/myApp",
  "protocol": "inspector",
  "sourceMaps": true,
  "sourceMapPathOverrides": {
    "/opt/myApp/*": "${workspaceFolder}/*"
  }
}

If your remote app uses compiled code (e.g., in a dist folder) with source maps pointing back to src files, adjust the override to match:

"sourceMapPathOverrides": {
  "/opt/myApp/dist/*": "${workspaceFolder}/src/*",
  "/opt/myApp/*": "${workspaceFolder}/*"
}

3. Verify Remote Node.js Debug Startup Flags #

Double-check that your container’s Node.js app is started with the inspect flag that allows remote connections:

node --inspect=0.0.0.0:9229 your-entry-file.js

Using 0.0.0.0 ensures the debug server listens on all network interfaces (critical for remote access from your Windows machine). Avoid --inspect-local as it restricts access to the container’s localhost.

4. Manually Map Scripts If Needed #

If you still see only VMxxxxx scripts in the "Loaded Scripts" panel:

• Right-click the VMxxxxx entry in the debug panel
• Select Map to Local File
• Navigate to the corresponding local file you copied in step 1
  This forces VSCode to link the remote runtime script to your local source, and future breakpoints on that file will work.

Once you’ve done these steps, you should see all your app’s source files in the "Loaded Scripts" panel, be able to set breakpoints without adding manual debugger statements, and have full read access to the synced remote code.

内容的提问来源于stack exchange，提问作者rfossella