microsoft / microsoft/vscode-js-debug
Provide additional path mappings, beside root in the attach configuration
@connor4312 is already working on this.
Since Feb 15, 2023.
- Dominant language
- TypeScript
- Stars
- 2k
- Forks
- 373
- Avg merge
- 1d 9m
- Merged PRs (30d)
- 6
Description
Is your feature request related to a problem? Please describe.
This is my launch config to attach a remote debugger to an application deployed in Cloud Foundry:
{
"name": "Attach to a Cloud Foundry Instance on Port 9229",
"port": 9229,
"request": "attach",
"type": "node",
"localRoot": "${workspaceFolder}",
"remoteRoot": "/home/vcap/app"
},
Cloud Foundry's NodeJS buildpack will install dependencies in /home/vcap/deps/0/node_modules.
I cannot hit breakpoints that I set in my local node_modules directory tree as the launch config is set to map the root to /home/vcap/app.
Describe the feature you'd like
I would like to have the possibility to map specific paths other than root.
At the moment my suboptimal workaround is Node.js debugging via Chrome, where I am able tot navigate the remote structure and set breakpoints in /home/vcap/deps/0/node_modules.

Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.