Vetur: Getting Property 'x' does not exist on type .... .Vetur(2339)
Info
- Platform: Win
- Vetur version: 0.24.0
- VS Code version:1.44.0-insider
Problem
adding properties inside a component breaks the known data and computed props and says Property 'x' does not exist on type 'CombinedVueInstance<Vue, object, object, object, Record<never, any>>'.Vetur(2339)
this can be a potential issue on next release of vscode maybe ?
Reproducible Case
Use veturpack and newest vscode-insiders
I can confirm it works properly with current stable release of vscode
jd1378
All 17 comments
it seems to be fixed now (probably vscode's fault)
jd1378
on 15 Apr 2020
I've been searching for information on this problem for two days now. This is _EXACTLY_ what is happening to me and it is quite annoying. As far as I can tell everything works OK, just lots of ugly red squigglies in my source. See my environment at the bottom of this post. I believe I have the latest of everything.
I see that the latest post here (prior to this one), on 2020-07-09, shows that the problem apparently still exists (for @mamedun). I also see it says CLOSED next to his post. This is all new to me (posting to GitHub) so not sure if his post was explicitly closed or implicitly closed because the thread was closed on 2020-04-15 by @jd1378. I guess I will probably find out as soon as I click green "Comment" button.
Here is my error: (oh, and I get this error in exactly the way the demo screenshot above shows)
[Property 'myProperty' does not exist on type 'CombinedVueInstance
macOS Catalina (10.15.5)
VS Code: 1.48.1 (Update says this is the latest)
Vetur: 0.26.1 (should I fall back to version 0.24?)
Not sure why this is closed unless it is (no longer) an issue on Windows
wkc1952
on 23 Aug 2020
Setting "vetur.experimental.templateInterpolationService" to false solved this issue for me.
red-meadow
on 31 Aug 2020
If you are having computed properties, you would need to annotate them (with JSDocs): https://vuejs.org/v2/guide/typescript.html#Annotating-Return-Types
Otherwise TypeScript is unable to infer this type.
Even though you are writing JS, Vetur is using TS to support it.
octref
on 1 Sep 2020
Weird, this just started happening to me today. MacOS Catalina. Setting vetur.experimental.templateInterpolationService like @red-meadow suggested doesn't work for me. It was disabled already, and toggling doesn't seem to have any effect.
I wonder what has changed where to cause this...
Petercopter
on 3 Sep 2020
me too
achimdan
on 3 Sep 2020
There is a new setting called vetur.validation.interpolation in 0.27.
Description:
Validate interpolations in region using TypeScript language service
rchl
on 3 Sep 2020
Having this issue as well, vetur.experimental.templateInterpolationService was disabled. Code works perfectly fine, but the code minimap gets lit up like a Christmas tree. At least it's in season I guess.
darzove
on 18 Dec 2020
disable vetur.validation.interpolation . Waring is not show, but hint is not work :disappointed:
mkidsc1603
on 31 Dec 2020
If you are having computed properties, you would need to annotate them (with JSDocs): https://vuejs.org/v2/guide/typescript.html#Annotating-Return-Types
Otherwise TypeScript is unable to infer
thistype.
Even though you are writing JS, Vetur is using TS to support it.
I was having troubles with this as well. I solved it following what they sent i.e. by annotating the return type of computed properties.
dertrockx
on 11 Jan 2021
Setting "vetur.validation.script" to false solved this issue for me.
xingorg1
on 28 Jan 2021
Change to false "vetur.validation.script" solved for me. Thanks.
gabrielxpinheiro
on 29 Mar 2021
Setting "vetur.validation.script" to false solved this issue for me.
This seemed to solve to squiggly lines.
But the intellisense is still missing for me until I write this.$xyz.
ShubhamVerma1811
on 30 Mar 2021
You can't disable validation and still have intellisense. Those go together.
Enable validation and fix type issues instead. How? It depends on your code but typically you have to add type annotations in various places.
Also see https://github.com/vuejs/vetur/blob/master/docs/guide/FAQ.md#property-xxx-does-not-exist-on-type-combinedvueinstance
rchl
on 30 Mar 2021
@rchl
Oh I didn't knew that
But I am facing the error in my script tag
Doing Object.keys(context) in asyncData shows that I have the $axios hook present, but doing context.$ shows no types
But by destructuring {$axios} and using this.$axios. shows intellisense again
It weird why my types arent working
ShubhamVerma1811
on 30 Mar 2021
Types is not a runtime thing. What you see at runtime is not gonna match types if you don't have types set up properly.
That's not a problem related to Vetur. Please ask for help in Nuxt discord, for example (https://discord.com/invite/ps2h6QT).
rchl
on 30 Mar 2021
I restart my computer for n times :<, tried all you guy say and nothing seems work :<
vanviethieuanh
on 26 Apr 2021
Related issues
pdanpdan
路
3Comments
Dealerpriest
路
3Comments
AnnAngela
路
3Comments
tczhangzhi
路
3Comments
shaunc
路
3Comments
Most helpful comment
There is a new setting called
vetur.validation.interpolationin 0.27.Description: