Getting Property 'x' does not exist on type .... .Vetur(2339)
See original GitHub issueInfo
- 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
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:23 (2 by maintainers)
Top Results From Across the Web
Property 'method' does not exist on type 'Vue'.Vetur(2339 ...
Vetur (2339) when trying to access parent method from child component (with class-based vue components) Save this question. Show activity on ...
Read more >[Help] Property 'x' does not exist on type ... - Reddit
I am having an issue with Nuxt and TypeScript tutorial. Nuxt build throws these errors. ERROR in components/Description.vue:138:10 TS2339: ...
Read more >React: Property 'X' does not exist on type 'Readonly<{}>'
The React.js error "Property does not exist on type 'Readonly<{}>'" occurs when we try to access the props or state of a class...
Read more >♂️ ♀️ Vue 3 error with using TypeScript: property X does ...
In this case, it is the input field, so its object will be called HTMLInputElement .
Read more >FAQ | Vetur - GitHub Pages
If you are getting a lot of Property 'xxx' does not exist on type 'CombinedVueInstance' errors, it's an issue with Vue's typing and...
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
There is a new setting called
vetur.validation.interpolation
in 0.27. Description:Setting “vetur.experimental.templateInterpolationService” to
false
solved this issue for me.