microsoft / microsoft/vscode-azurestaticwebapps
Vue.js debugging can't set/hit breakpoints
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 99
- Forks
- 39
- Avg merge
- 3d 7h
- Merged PRs (30d)
- 2
Description
Vue.js and the VS Code debugger have a long history of simply not working well, as noted in the docs. The issue stems from the way Vue.js creates source maps.
It's really inconsistent and seems like many users are still having issues setting/hitting breakpoints using the built-in JavaScript debugger in .vue files.
I'm not sure we can fix on our end, however I want to track it here because I'm hopeful we can get some help from other teams to solve the issue.
Contributor guide
No contributing guide indexed for this repository
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 linked VS Code Vue.js debugging documentation and the vue-loader source-map issue, then reproduce breakpoint behavior in .vue files with the built-in JavaScript debugger. Done would require determining whether this repository can fix the inconsistency or coordinating a fix with the relevant external team.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, vscode
- Domain
- devtools, frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100