-
-
Notifications
You must be signed in to change notification settings - Fork 500
Open
Labels
Description
Vue - Official extension or vue-tsc version
v3.14
VSCode version
1.106.0
Vue version
3.5.24
TypeScript version
5.9.3
System Info
System:
OS: Linux 6.17 Garuda Linux
CPU: (8) x64 Intel(R) Core(TM) i7-7700 CPU @ 3.60GHz
Memory: 25.71 GB / 31.29 GB
Container: Yes
Shell: 4.2.1 - /usr/bin/fish
Binaries:
Node: 22.19.0 - /usr/local/bin/node
npm: 11.6.2 - /usr/local/bin/npm
Browsers:
Brave Browser: 142.1.84.139package.json dependencies
"dependencies": {
"@nuxt/content": "^3.8.0",
"@nuxt/fonts": "^0.12.1",
"@nuxt/icon": "^2.1.0",
"@nuxt/image": "^2.0.0",
"@nuxt/scripts": "^0.13.0",
"@nuxt/test-utils": "^3.20.1",
"@pinia/nuxt": "^0.11.3",
"@unhead/vue": "^2.0.19",
"axios": "^1.10.0",
"better-sqlite3": "^12.4.1",
"bootstrap": "^5.3.7",
"bootstrap-icons": "^1.13.1",
"netlify-cli": "^23.9.0",
"nuxt": "^4.2.1",
"pinia": "^3.0.4",
"tinacms": "^2.9.0",
"vue": "^3.5.24",
"vue-router": "^4.6.3"
},
"devDependencies": {
"@tinacms/cli": "^1.11.0",
"@types/node": "^24.10.0",
"@vitejs/plugin-vue": "^6.0.0",
"@vitejs/plugin-vue-jsx": "^5.0.0",
"sass": "^1.89.2",
"standard-version": "^9.5.0",
"typescript": "^5.9.3",
"vite": "^7.0.0",
"vite-plugin-vue-devtools": "^7.7.7"
}Steps to reproduce
Steps to reproduce the error
- Download the latest update.
- Open a file e.g App.vue
What is expected?
The Vue - Official extension (Volar) should provide correct syntax highlighting for all language regions within a Vue Single File Component (SFC).
Specifically, this includes:
- HTML/Vue syntax highlighting within the block.
- TypeScript syntax highlighting within the <script lang="ts" setup> block.
- JavaScript syntax highlightning within the <script setup> block
What is actually happening?
After upgrading to 3.1.4, the entire .vue-file content, including both <template> & <script> tags, appears as plain text.
Link to minimal reproduction
Just open a random .vue-file
Any additional comments?
Workaround / Temporary Fix
The issue can be temporarily resolved by manually downgrading the Vue - Official extension to the previous version, v3.1.3.
However, the problem automatically reappears when the extension updates back to the faulty version v3.1.4, indicating a regression in the latest release.