-
I enjoy not having to import all the component files. Though, it seems to me, that a lot of the Intellisense stops working if I do not explicitly import a component in the script tag.
Is there any…
-
See https://vuejs.github.io/vetur/guide/vti.html
There's a fair amount of errors this spits out, so I don't have time to go after this now. However, it should be a relatively straightforward to wor…
-
## Background
I recently transitioned from using Vue 2 (generation using: "**vue-cli**", and using vscode extension: "**Vetur**") in my projects to the new Vue 3. This new project was set up using th…
-
So, Can I Use Which plugins in Vscode Now?
tyzma updated
4 years ago
-
Right now Vetur is way too harsh on the imports and typescript linting, thinking that there's unclosed tags or something to that effect. I've tried a few copy/pastes of configs, but I need something …
-
## Feature request
- [ ] Linting for config files
- [ ] Vetur autocompletions and templates for the customized Vue parts (like `export const data = {}`)
#### What problem does thi…
-
I was wondering if there are any plans for supporting vetur.config.js?
It's critical for monorepo support with tsconfig.json living in a subfolder. https://vuejs.github.io/vetur/reference/
I'm i…
-
In a Vue3/Typescript project, Vetur (VSCode) shows the following error when using this plugin:
> Property 'VueLogo' does not exist on type '{ $: ComponentInternalInstance; $data: {}; $props: Partia…
-
package.json
"eslintConfig": {
"root": true,
"env": {
"node": true
},
"extends": [
"plugin:vue/essential",
"eslint:recommended",
"@vue/prettier"
…
-
**Is your feature request related to a problem? Please describe.**
Since Vue component templates in VSCode do not have typescript support, it's difficult to consume component libraries without consta…