Replies: 2 comments
-
Vue's source maps are incorrect. This is also causing coverage issues for There are some similar reports on vuejs/vue-loader#1778 but I was unable to get this working using the work-around mentioned on that issue. If you find out the root cause or solution for this please let me know. |
Beta Was this translation helpful? Give feedback.
0 replies
-
I have exactly the same problem: #5380 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm having problem debugging components with Vitest, I'm not sure if this is bug or bad configuration.
For this demo I'm using the Hello.vue from vitest/examples and test basic.test.ts.
In vs-code I've added this launch setting:
None of configs or files from the Vitest example is modified.
In Hello.vue I add a breakpoint at line 6 (the ref). Then I launch the debugger and all is good, and it stops at correct line :-)
However Hello.vue is simple, and as soon as I add a e.g. a style to the component, the breakpoint stops at incorrect line number ( unbounded ). See below for the modified component, the breakpoint is still set to line 6, but it stops at line 12.
It seems that there is something odd with the source map?
I've tried to add
sourcemap: 'inline'
to vitest.config.ts, however it does not change behaviour. I tested The VS code debugger with Vite and Chrome at this hits correct line number. This issue is only happening during VitestDoes any one have a valid setup/configuration to debug components during vitest?
Beta Was this translation helpful? Give feedback.
All reactions