Vite doesn't show TypeScript errors/warning until build time

[iaseth]

While vite is awesome in terms of speed and disk space, I ran into a bit of a problem with it in my React+TypeScript project. npm run dev works well but just ignores any bad/missing type definitions, but when I run npm run build, it shows all the errors/warnings correctly.

My package.json "scripts" is as follows:

"scripts": {

  "dev": "vite --host",

  "build": "tsc && vite build",

  "preview": "vite preview",

  "lint": "eslint . --ext .tsx"

}

How do I get vite to show all TypeScript and ESLint errors during development?

[yann-combarnous]

The documentation explains how to do this pretty clearly: https://vitejs.dev/guide/features.html#transpile-only

[iaseth]

I guess there are pitfalls of using a tool without reading its documentation :)
Thanks for answering.

[timrobinson33]

It's worth pointing out that when used as directed, vite doesn't detect typescript errors even at build time

The documentation says "When it is time to deploy your app for production, simply run the vite build command" but this ignores typescript errors too. The OP has used tsc && vite build which does detect typescript errors.

[yann-combarnous]

Yep, even though Vite can transpile Typescript with Esbuild/Swc and remove all TS decoration, it does not understand it.

[adamjhickey]

vite-plugin-checker works for my main TypeScript app in my monorepo. However, when I make a change to a local package dependency while developing, it does not show type errors...

Anyone have a similar issue? I was trying to avoid starting a watch process for the packages being worked on, considering they can have multiple local package dependencies as well.

[vtsvetkov-splunk]

This worked for me
fi3ework/vite-plugin-checker#382 (comment)