You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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 runningvite
(ie. dev mode) it shows warnings: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.
The text was updated successfully, but these errors were encountered: