VS Code Woes (Intellisense, ESLint, etc.) #650
Unanswered
codeflorist
asked this question in
Q&A
Replies: 2 comments 2 replies
-
Antfu's config is good, but it's H E A V Y, five times more so especially if you try to use type-aware in vue |
Beta Was this translation helpful? Give feedback.
1 reply
-
are you already fix this issue @codeflorist? |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I have a Nuxt setup trying to use the best pratices and work with VS code. My setup is essentially:
package.json:
VS code extensions:
I'm having major problems with this setup. Stuff seldomly works. After a VS code restart it normally works. But after a while
goto-alias
stops working, Intellisense stops working, sometimes VS code suddenly shows the messageExtension
ESLintis configured as a formatter but it cannot formatn 'vue' files
out of the blue, when calling the "Format document" command on a vue-file (often just one single VUE-file, and not any others??). Intellisense is just showingLoading
everywhere. "Format document" ist doing something eternally without any effect. After a restart it works again for a short while.It makes the whole dev-experience an excruciating mess.
Does anyone have any idea, what could cause these issues? Does anyone other experience these problems? I've been basically trying to get a hassle-free dev-environment using eslint, vs code and nuxt to work for years now.
Beta Was this translation helpful? Give feedback.
All reactions