Closed Mass1milian0 closed 8 months ago
in addition to that, seems like reloading the entire IDE dose make nuxtr realize this file needs linting, but that doesn't mean we should be forced to reload every time we create a new page in a subfolder of pages
Hi, Nuxtr doesn't have anything to do with linting at all except for a command Nuxtr: Configure Linters
to configure ESLint or Stylelint. And from your description here, this is not a linting issue as much as it's a TypeScript one.
For Nuxt to offer a great DX, it generates good number of files including a tsconfig.json
file inside .nuxt
directory along with types so your IDE can detect and map files and everything else.
Sometimes this generation process can be outdated or having issues, and using npm run postinstall
can fix this issue with new updated files.
But also it's recommended to enable TakeOver Mode.
Environment
Build Modules: -
What went wrong?
linter doesn't highlight components, and doesn't recognize things such as
definePageMeta
it's as if the extension complitely disableseverything works complitely fine in the browser of course, the page in that folder loads perfectly fine
How to reproduce it?
Create a folder in Pages in that folder, create a .vue file try using any nuxt function or component in that file