After upgrading from NUXT 3 Release candidate to the latest and released version and making the changes I needed in order to get everything running smoothly, vue-tsc has started showing an error-badge just before reporting 0 errors.
Do I actually have any errors, or is there something else going on here?
Is it vue-tsc logging the badge, or something else?
Versions
Nuxt: 3.2.2
vue-tsc: 1.1.5
typescript: 4.8.3
Going back to Nuxt 3.0.9-rc along with downgrading vue-tsc removes the "error".
I have the same issue with Nuxt 3.2.3 and vue-tsc 1.2.0. However, it raises only if I enable type check in development mode. I did this either by adding to
nuxt.config.json
the following option (like official Nuxt docs state here https://nuxt.com/docs/guide/concepts/typescript):or with vite-plugin-checker and
for
vite.plugins
property.In both cases an ugly red ERROR badge followed by 0 errors is still there.
I haven't found any solution so I've just removed this in-dev check from nuxt.config.json and rely on:
tsconfig.json
rules anywayseslint
andnuxi typecheck
in my case, though it can bevue-tsc --noEmit
as well).This way I can be sure no errors go to the repo while developers are still notified about them when writing their code.
I know this isn't an answer to your question (and probably not the best solution...) but just wanted to give more context for those who could probably clarify this one.