-
-
Notifications
You must be signed in to change notification settings - Fork 8.9k
Closed
vitejs/vite-plugin-vue
#585Labels
π¨ p3-minor-bugPriority 3: this fixes a bug, but is an edge case that only affects very specific usage.Priority 3: this fixes a bug, but is an edge case that only affects very specific usage.scope: sfc
Description
Vue version
3.5.13
Link to minimal reproduction
https://stackblitz.com/~/edit/vue-source-maps-off?file=index.mjs
Steps to reproduce
pnpm install
node index.mjs
# Check links in ./links.mdWhat is expected?
Source maps of all fixtures/*.vue files should contain correct mappings. Using the source map visualizer it is visible that files 1-4 contain incorrect mappings.
What is actually happening?
Source maps of first.vue, second.vue, third.vue and fourth.vue are broken. Only the fifth.vue has correct mappings.
first.vue: https://evanw.github.io/source-map-visualization#MTMyNABpsecond.vue: https://evanw.github.io/source-map-visualization#MTMyNgBpthird.vue: https://evanw.github.io/source-map-visualization#MTMyNABpfourth.vue: https://evanw.github.io/source-map-visualization#MTMyNgBpfifth.vue: https://evanw.github.io/source-map-visualization#MTM2MABp
System Info
https://stackblitz.comAny additional comments?
Bonus points if you can show me how to use Vue compiler directly without Vite. A minimal async function compile(sourceCode: string): { code: string, map: SourceMap }. β€
Metadata
Metadata
Assignees
Labels
π¨ p3-minor-bugPriority 3: this fixes a bug, but is an edge case that only affects very specific usage.Priority 3: this fixes a bug, but is an edge case that only affects very specific usage.scope: sfc