microsoft / microsoft/vscode-js-debug
Breakpoints showing "Unbound breakpoint" in VS Code when debugging React app
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2k
- Forks
- 373
- Avg merge
- 1d 9m
- Merged PRs (30d)
- 6
Description
I am trying to debug a React application in VS Code, but the breakpoints are not binding correctly.
When I set a breakpoint in my source file, VS Code shows "Unbound breakpoint" and displays the following message:
We couldn't find a corresponding source location, and didn't find any source with the name
Api_Call.js.
Project Details:
- Framework: React
- Start command:
npm start - File where breakpoint is set:
src/CONNECTION/Api_Call.js - OS: Windows
- Editor: VS Code
Current launch.json configuration:
{
"version": "0.2.0",
"configurations": [
{
"name": "Launch Chrome",
"request": "launch",
"type": "chrome",
"url": "http://localhost:3000",
"webRoot": "${workspaceFolder}"
},
]
}
<img width="792" height="188" alt="Image" src="https://github.com/user-attachments/assets/2b98fb0d-b629-49cb-8f40-6c90ad80fd0f" />
Issue:
VS Code cannot map the running code in the browser to the local source file, and the breakpoint remains unbound.
Steps to Reproduce:
- Start the React application using
npm start. - Launch the debugger in VS Code.
- Set a breakpoint in
Api_Call.js. - Breakpoint appears hollow and shows "Unbound breakpoint".
Expected Behavior:
Breakpoints should bind correctly and pause execution when the code is hit.
Actual Behavior:
Breakpoints remain unbound and the debugger does not stop.
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.
Research direction
Start with the launch.json configuration and the React app entry point run by npm start, then reproduce the unbound breakpoint in src/CONNECTION/Api_Call.js using the Launch Chrome configuration. Compare the browser's loaded source to the local file and determine why Api_Call.js cannot be mapped; done means the breakpoint binds and pauses when execution reaches it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react, vscode
- Domain
- devtools, frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100