Open bonham opened 6 months ago
Can you test if @vitejs/plugin-vue@4.5.2
works?
This issue has come up before - it's not really Vitest related. I would guess that your breakpoints don't work even when debugging in browser during development.
Related discussions:
This is most often related to bad or missing sourcemaps
Can you test if
@vitejs/plugin-vue@4.5.2
works?
No, it has the same bug.
This issue has come up before - it's not really Vitest related. I would guess that your breakpoints don't work even when debugging in browser during development.
Breakpoints work well in browser. Breakpoints work well starting vite dev server in "Javascript debug terminal". So it's pretty much narrowed down to vitest I'd say.
Related discussions:
* [Coverage issue in vue files when upgraded with version 1.1.3 or 1.2.0 #4991](https://github.com/vitest-dev/vitest/discussions/4991)
^ This is not related to breakpoints
* [How to debug compents while running tests in VS code? #2874](https://github.com/vitest-dev/vitest/discussions/2874)
^ this is describing exactly the same problem.
Source maps are turned on as you can see in my minimalistic example: https://github.com/bonham/vitest-debug-issue-js/blob/main/vite.config.js
Breakpoints seem to work fine when using Chrome Dev tools:
https://github.com/vitest-dev/vitest/assets/14806298/d38cffaa-0529-4006-94ad-6818fdb8df47
Hi @AriPerkkio, yes you are right. I tried the same and also for me breakpoint works well. This is a good workaround. ( I never tried debugging this way before: https://vitest.dev/guide/debugging#node-inspector-e-g-chrome-devtools )
Summary:
Idk, but seems not a vitest issue but maybe a vs-code issue ( vue plugin or whatever .... )
Not sure if this is helpful or not, but I can reproduce this issue (in the VS Code debugger) without vue at all, just a plain node app. Disabling coverage when a debugger is attached is a workaround but unfortunate.
Not sure if this is helpful or not, but I can reproduce this issue (in the VS Code debugger) without vue at all, just a plain node app. Disabling coverage when a debugger is attached is a workaround but unfortunate.
with vitest or even without vitest?
@bonham Oh sorry, yes with vitest.
I just tested debugging in VS Code with a node app instrumented with istanbul and esbuild and it works fine with breakpoints being where they should be. So I think there's something in vitest specifically that is causing the problem, I don't think that VS Code is the root problem (although maybe a contributing factor).
@CreativeTechGuy how can I reproduce this issue? Is it with covearge.provider: 'v8'
or covearge.provider: 'istanbul'
? Does it work with vitest --inspect-brk
?
@AriPerkkio Sorry for the delay, this is gnarly. I couldn't reproduce it starting from an empty repo, but I started deconstructing my massive repo and I was able to get it down to a few dozen lines total across all files. I've put a ton of information and very detailed steps in the repo README. Let me know if you are able to reproduce. I've been able to reproduce it across two computers (Windows 10 & 11) so far so hopefully you can too.
https://github.com/CreativeTechGuy/vitest-coverage-debugger-issue-repro
Hi @AriPerkkio, yes you are right. I tried the same and also for me breakpoint works well. This is a good workaround. ( I never tried debugging this way before: https://vitest.dev/guide/debugging#node-inspector-e-g-chrome-devtools )
Summary:
- breakpoints work well when using node inspector and chrome devtools
- breakpoints do not work when running vitest in debug mode within vs-code ( I tested on mac and windows )
Idk, but seems not a vitest issue but maybe a vs-code issue ( vue plugin or whatever .... )
We are experiencing this same problem at the moment and for us the workaround going through the Chrome Devtools is also working, but a lot less convenient to use.
We have this issue at our work across multiple VueJS and Nuxt projects. Various developers have spent collective weeks trying to solve to no success.
There's some more discussion about VS Code not respecting inline source maps here: https://github.com/vitest-dev/vitest/issues/5605. Check the solution at the end and see if it works for you.
Not sure if the solution at the end is quite our problem - they seem to be trying to debug node_modules, where we are failing on our application code. Trying their fix of this.showExternalized
didn't fix anything :( Tried it on two separate projects.
Issue goes away when removing section in .vue file
To me this sounds like source mapping issue. As soon as I remove <style>
tags from *.vue
files, VS code debugger starts to work. It's like if the <style>
tag is introducing another transform step that messes up the source maps completely.
But when looking at the source maps they look just fine:
So to summarize:
We have quite many issues that are related to VS Code not being able to handle source maps. Does Vue debugging work in VS Code in general, without Vitest?
We have quite many issues that are related to VS Code not being able to handle source maps. Does Vue debugging work in VS Code in general, without Vitest?
By default, Vitest strips all CSS styles. Does debugger work if test.css
is enabled?
Having the same issue with an angular application. Breakpoints are all messed up when debugging tests. Works perfectly when debugging application ran with ng serve.
Describe the bug
In vanilla project with vue3 + vitest + @testing-library/vue + node 18.18.2 or 20.11.1, setting and debugging breakpoints in vs-code on windows 11 does not work as expected. Debugger stops at wrong location. I am using vue single file components ( aka .vue files )
Seems to be transpiling and/or sourcemap issue.
The issue disappears when removing section in .vue file
Reproduction
Issue goes away when removing section in .vue file
Example file
SimpleComponent.vue
Example
simple.spec.js
Full example vanilla project to clone and reproduce: https://github.com/bonham/vitest-debug-issue-js
System Info
Used Package Manager
npm
Validations