-
-
Notifications
You must be signed in to change notification settings - Fork 6.6k
Sourcemap in dev mode #8289
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
Labels
Comments
I have it too. I don't know if we changed something or if we didn't take a good look before (and I'm sorry if we did) ... but the sourcemap in dev mode is displayed correctly. Thank you for your time ! |
Thanks for the update @CarolineSenes, lets close this issue then 👍🏼 |
I think the issues is not fix.
you can see null in console. |
@poyoho I think that is an different issue which needs to be fixed. |
ok. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Clear and concise description of the problem
I'm working with a team migrating a project from Webpack to Vitejs. Currently, sourcemap in dev mode is only displayed when there is an error in the console (i'm not talking about the CSS sourcemap). When you click on the file that contains the error, the sourcemap opens.
github minimal reproduction
Suggested solution
I don't know how, but it would be useful to be able to always (even if there is no error) view the sourcemap in dev mode with options like in webpack (eg: eval-source-map).
Alternative
No response
Additional context
Vite / React
Validations
The text was updated successfully, but these errors were encountered: