VS Code Woes (Intellisense, ESLint, etc.)

[codeflorist]

I have a Nuxt setup trying to use the best pratices and work with VS code. My setup is essentially:

package.json:

@antfu/eslint-config,
@nuxt/eslint

VS code extensions:

"Vue.volar",
"bradlc.vscode-tailwindcss",
"esbenp.prettier-vscode",
"dbaeumer.vscode-eslint",
"lokalise.i18n-ally",
"antfu.goto-alias"

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 message Extension ESLint is 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 showing Loading 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.

[Dimava]

• Restart ESLint from Ctrl+Shift+P
• Give it some time. It has to load a lot of stuff
• Try disabling vue/typescript/both in eslint and check how it works. type-aware eslint rules in Vue are veeery slow.
• Set "eslint.debug": true in config json and check what does ESLint plugin says in its Output terminal tab when loading

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

[codeflorist]

Many thanks for those tips! I'll try them out