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
Describe the bug
Since installing Deno extension, Vue's component highlighting has stopped working and is displayed in the same color as default HTML5 tags. Intellisense functions properly, and I have confirmed that highlighting works correctly when Deno is uninstalled.
I can confirm this issue. I have the Deno extension installed and enabled only within my Deno project’s settings. However, setting "deno.enable": true in that project causes incorrect syntax highlighting for Vue files in a completely different project within the same workspace (even though that other project has no reference to Deno).
I also tried using "deno.enablePaths" and "deno.disablePaths" instead of "deno.enable", but it made no difference. As soon as the Deno extension is installed, Vue’s syntax highlighting is negatively affected in the other projects—regardless of how I configure the Deno settings.
Deactivating the Deno extension, or even setting "deno.enable": false in the Deno project folder, immediately restores the correct Vue syntax highlighting for the other projects.
Edit: This issue occurs in version 3.43.1. It did not occur in 3.43.0, where everything worked perfectly with correct Vue highlighting and no issues.
Describe the bug
Since installing Deno extension, Vue's component highlighting has stopped working and is displayed in the same color as default HTML5 tags. Intellisense functions properly, and I have confirmed that highlighting works correctly when
Deno
is uninstalled.To Reproduce
Vue - Official
extensionDeno
extensionExpected behavior
The custom component highlighting in Vue needs to work properly.
Screenshots
Before installing Deno
After installing Deno
Versions
vscode: 1.93.0 deno: 2.1.4 extension: 3.43.1
Vue - Official: I have confirmed the same symptom in all versions from 2.2.0 to 1.8.27.
The text was updated successfully, but these errors were encountered: