Extension Does Not Work Properly With Vite
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- typescript, vite, vscode
- Domain
- devtools
Research direction
No repository file or test is named. Start with the smaller Vite example mentioned in the issue and compare breakpoint behavior with react-scripts in VS Code; progress would require a reproducible case documenting incorrect lines, unrelated stops, or phantom breakpoints.
Written by the indexing model from the issue text.
Description
I am currently using react-scripts start to run my React app. I am able to set and hit breakpoints and everything works as expected. We are switching to using Vite and after updating our build process to use Vite breakpoint debugging has become unusable. Because my code is proprietary, there is no way I can post it as an example, and while I do have a smaller example that exhibits odd debugger issues, I can't get an exact repro for every case.
The issue we are seeing is that after moving to Vite, line numbers that are reported in VS Code when hitting an exception are just plain wrong. Like wildly wrong. In other cases we will set a breakpoint in a file and the debugger will stop on a completely unrelated line. In other cases the debugger will simply stop at phantom breakpoints.
Before I go through the arduous process of creating an example repo in github or something to try to create a project that reproduces these issues, can someone confirm whether this is a known issue and has a work-around? Or if anyone else is experiencing this?
To confirm. switching back to react-scripts everything works as expected, but using Vite, breakpoints don't work consistently.
- Dominant language
- TypeScript
- Stars
- 447
- Forks
- 76
- PR merge metrics
- No merged PRs in 30d
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.
More from firefox-devtools/vscode-firefox-debug
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
firefox-devtools/vscode-firefox-debug#391 · 2 comments · 1 reaction ·
-
bug path mapping
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
Castle Open
Difficulty 5/5 Over a week Newbie friendliness 10/100
-
Create new issue Open
Difficulty 5/5 Over a week Newbie friendliness 1/100
All issues in firefox-devtools/vscode-firefox-debug
Similar issues
-
VerificationGate: ATTRIBUTION quote guard never matches a normal quotation (\b around the quote) Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
danielmiessler/LifeOS#2234 ·
-
T: Bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
-
Mend: dependency security vulnerability untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 70/100