Skip to content
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

Sourcemap issues when used with Vite #10

Open
baffalop opened this issue Apr 24, 2023 · 0 comments
Open

Sourcemap issues when used with Vite #10

baffalop opened this issue Apr 24, 2023 · 0 comments

Comments

@baffalop
Copy link

I tried to use this plugin with Vite to transform Vue files prior to passing to @vitejs/plugin-vue, but it appears to interfere with the production of sourcemaps. In the terminal running vite (ie. dev mode) it shows warnings:

Sourcemap for "/var/www/tpf/node_modules/vite/dist/client/client.mjs" points to missing source files
Sourcemap for "/var/www/tpf/node_modules/vite/dist/client/env.mjs" points to missing source files

And in the browser console, any warnings or errors show stack traces where most stack frames have a null filename reference, ie. null:138. When there is a reference to a Vue file, this will point to the compiled output file (with inaccurate line numbers) rather than the mapped Vue single-file component as expected.

I'm unsure if this is an interaction between this plugin and the Vue plugin, or with Vite in general.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant