Vue-TSC Error spam every time pnpm/npm dev is used in a new project.
Good afternoon,
I have tried to setup a new personal website for start a new project. After creating a new project using the
pnpm/npm nuxt@latest I then follow the documentation, I ran the following commands install --save-dev vue-tsc typescript, nuxt typecheck, andnuxt prepare. I have also added typeCheck: true in the c onfig and tried typescriptPlugin enabled and disabled.
Ive tried to search around for answers like I did with another issue I had a few days back but I have been unable to find any potential solutions to attempt. I am fairly clever in tech and IT in general, however, I feel out of my depths trying to resolve this issue and may be beyond my mental capabilities (disabilities), I would really appreciate some assistance with resolving this or direction towards solving this, thanks.
Here are the errors I am getting:
Multiple missing types like these.
Missing files x2 (Second one often shows up multiple times when dev mode is kept running running)
2 Replies
Hi @ModernKiwi. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
These errors match a known Nuxt +
The sources don’t provide an exact, stable combination of Nuxt/Nitro/vue-tsc that fully removes all the spam, so I can’t give a guaranteed “good” set beyond the Nuxt
vue-tsc + vite-plugin-checker problem, especially on Windows, where the TypeScript lib files inside vite-plugin-checker are missing and basic globals like Boolean, Object, CallableFunction, etc. cannot be found. [Windows build issue]
From the reports:
- Errors like Cannot find global type 'CallableFunction', Cannot find name 'Boolean' and missing lib.dom.d.ts / lib.dom.iterable.d.ts are exactly what you’re seeing. [Windows build issue]
- The problematic path is node_modules/vite-plugin-checker/dist/checkers/vueTsc/typescript-vue-tsc/lib/..., again matching your logs. [Windows build issue]
- Several users confirm that downgrading Nuxt to 4.1.2 avoids the issue. [Windows build issue]
- Another user notes that updating Nitro to 2.12.9 fixed their build error, though they still see some npm run dev errors (likely environment-specific). [Windows build issue]
Given what’s in the sources, concrete workarounds that are known to help are:
1. Use Nuxt 4.1.2 temporarily
Pin Nuxt to 4.1.2 in package.json and reinstall:
Then run your package manager’s install again. Multiple users report this removes the vue-tsc spam on dev. [Windows build issue]
2. Ensure you’re on a version with the latest Nitro fixes
One user reports their build error disappeared after Nitro 2.12.9, though dev-time vue-tsc still had issues for them. [Windows build issue]The sources don’t provide an exact, stable combination of Nuxt/Nitro/vue-tsc that fully removes all the spam, so I can’t give a guaranteed “good” set beyond the Nuxt
4.1.2 workaround above.
3. If you stay on a newer Nuxt:
The knowledge sources don’t document a reliable, configuration-only fix (like a tsconfig tweak) that resolves these missing lib / global type errors when using current Nuxt + vite-plugin-checker. They only show that:
- It’s tied to vite-plugin-checker’s bundled typescript-vue-tsc libs.
- Downgrading Nuxt solves it for affected users.
Because of that, I can’t suggest a precise permanent fix beyond aligning your versions as in (1) or (2). If you need to proceed on the very latest Nuxt and the errors block you, the safest next step—based on what’s available—is:
- Temporarily disable in-editor/on-dev typechecking from vite-plugin-checker (e.g. turn off typeCheck in Nuxt config), and run npx nuxi typecheck manually when needed, while tracking Nuxt releases (e.g. patch releases like 4.0.3 and later) that touch typechecking and tooling. [v4.0.3]
If you can share your exact Nuxt/Nitro/Node/OS versions, that would help compare directly with the combinations reported in the linked issue, but within these sources the most consistent workaround is pinning Nuxt to 4.1.2.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------<@265401974449504257> Kapa.ai is still learning and improving, please let me know how I did by reacting below.