Vetur Vue Intellisense For Vue Template Displaying Red Color But Not Error
See original GitHub issueIssue Type: Bug
After updating VSCode to the January 2021 version, the Vue code that is in the <template> </template> tag partially turns red (because it’s usually due to a code writing error). the compile process runs normally without errors. It’s just uncomfortable seeing the previously normal code change color (as if it’s an error)
Extension version: 0.32.0 VS Code version: Code 1.53.2 (622cb03f7e070a9670c94bae1a45d78d7181fbd4, 2021-02-11T11:48:04.245Z) OS version: Windows_NT x64 10.0.19042
System Info
Item | Value |
---|---|
CPUs | Intel® Core™ i7-4790 CPU @ 3.60GHz (8 x 3592) |
GPU Status | 2d_canvas: enabled gpu_compositing: enabled multiple_raster_threads: enabled_on oop_rasterization: unavailable_off opengl: enabled_on protected_video_decode: unavailable_off rasterization: unavailable_off skia_renderer: enabled_on video_decode: enabled vulkan: disabled_off webgl: enabled webgl2: enabled |
Load (avg) | undefined |
Memory (System) | 15.89GB (11.68GB free) |
Process Argv | –crash-reporter-id f30efc2b-9351-478a-a544-4975aa18f426 |
Screen Reader | no |
VM | 0% |
A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383:30185418
pythonvspyt617cf:30253240
vspor879:30202332
vspor708:30202333
vspor363:30204092
vstry244:30256636
pythonvsdeb440:30248342
pythonvsded773:30248341
vstes627:30244334
pythonvspyt600cf:30251589
Issue Analytics
- State:
- Created 3 years ago
- Reactions:9
- Comments:10 (1 by maintainers)
Top Results From Across the Web
Vetur marks first line of .vue file as an error
I see an ESLint error The template root requires exactly one element . What versions of VS Code and Vetur are you using?...
Read more >Vue JavaScript Tutorial in Visual Studio Code
Vue JavaScript tutorial showing IntelliSense, debugging, and code navigation support in the Visual Studio Code editor.
Read more >IntelliSense | Vetur - GitHub Pages
Vetur offers IntelliSense for html tags & attributes. Vetur also completes Vue specific attributes such as v-if and @click . Inside template interpolation ......
Read more >Configuring VS Code for Vue Development
Vetur ; Installing Vetur; Syntax highlighting; Snippets; IntelliSense; Scaffolding; Emmet; Linting and error checking; Code Formatting ...
Read more >vetur 2307 - You.com | The search engine you control.
console.log(variable) // there is no error in the console but, it work normally in ... I get the following error from Vetur when...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I have the same issue since the last update. It seems to be doing if I use the
typeof lightbox !== 'undefined'
in the template. When I change it to the(typeof lightbox) !== 'undefined'
then the problem disappear. First way without brackets is valid and vetur should not force us to change the way we are writing the code.Still an issue… with vetur 0.34. I’m patching this by enclosing typeof statement with parentheses: (typeof yocrazy !== ‘undefined’)