-
Notifications
You must be signed in to change notification settings - Fork 58
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The number of lines that use vite-plugin-style-import to cause debugging to point to errors. #11
Comments
I can't find a solution to this problem temporarily |
I tried to use magic-string to generate sourcemap, but it still doesn’t work |
Is it because the sourcemap has been generated before the dependency is introduced? |
@joker77877 Try to upgrade to 0.8.2 |
What happened?Version 0.8.1 works well. |
This question was automatically closed just now. 0.8.3 restores the 0.8.2 modification |
OK.Looking forward to your repair. |
@joker77877 Try to upgrade to 0.9.0 |
It works.Thanks. |
This problem occurs again when upgrading to the latest version. |
I occured the same problem, after some research I found that this plugin reads vite config |
workaround not works for me. |
@zzjin try to force restart dev-server. if it still doesn't work, there maybe a problem with another plugin you use. |
Chrome's devtool debugger points to wrong locations in source files.
Create new vue-ts project with Vite.
yarn create @vitejs/app my-project --template vue-ts
Add a debugger in source code and run app in Chrome (yarn dev). See breakpoint trigger but pointing at wrong line/location.
In this image, should be pointing at line with debugger;
Repo with reproduction here: https://github.com/joker77877/vite-vue3-sourcemap-issue.git
Run yarn dev and view localhost:3000 in Chrome with devtools open.
The text was updated successfully, but these errors were encountered: