vite-plugin-checker: Plain Vite Shipped My TS Error

I injected one deliberate TypeScript error into a 122-module Vite 7.3 React app: plain vite build still exited 0 and wrote dist, while vite-plugin-checker 0.10 with enableBuild: true failed with exit 2. On clean builds the checker median was 2,018 ms against 1,949 ms for plain Vite (+69 ms) and 985 ms for a separate tsc --noEmit.

Short answer: turn the checker on for production builds if you do not already fail CI on tsc --noEmit. The cost here was under 4% of wall time; the win is that Vite alone will happily ship code that TypeScript rejects. No affiliate links in this post.

What I tested

• Machine: 8 vCPU Intel Xeon / 15 GB RAM shared Linux cloud box, tested 6 Oct 2026 about 00:05–00:10 IST.
• Versions: Vite 7.3.6, vite-plugin-checker 0.10.3, TypeScript 5.9.3, React 19.3.0, Node 22.20.0. Config: @vitejs/plugin-react plus checker({ typescript: true, enableBuild: true }).
• Fixture: /workspace/bench-vite-checker/. 60 lib modules, 60 page components, App + main (122 source files). Production builds cleared dist and Vite caches between runs.
• Timing: wall clock around each process via the local Vite and tsc binaries (no npx). One warm-up, then 7 interleaved clean rounds for plain Vite, checker Vite, and tsc --noEmit. Then 3 rounds with a number = "not-a-number" error in P0.tsx.
• Findings: clean medians plain 1,949 ms, checker 2,018 ms (+69 ms), tsc 985 ms. With the type error: plain Vite exit 0 three times, checker exit 2 three times, tsc exit 2 three times.
• One surprise: checker wall time on the broken build (1,868 ms median) was in the same band as a clean checker build. Failing fast did not cost extra here.
• Not tested: ESLint overlay, vue-tsc, overlay UX in vite dev, incremental tsc -b, monorepo project references, Windows or macOS.

Does plain Vite ship TypeScript errors?

Run (122 modules)	Exit	Ships dist?	Wall median
vite build (clean)	0	yes	1,949 ms
vite build + checker enableBuild (clean)	0	yes	2,018 ms
tsc --noEmit (clean)	0	n/a	985 ms
vite build (TS error in P0)	0	yes	1,895 ms
checker enableBuild (TS error in P0)	2	no	1,868 ms
tsc --noEmit (TS error in P0)	2	n/a	1,101 ms

Yes. esbuild strips types, so a bad assignment is invisible to the bundler. My broken P0 still produced a full dist with the same asset shape as a clean build. That is the whole reason to add a typecheck gate somewhere in CI or at build time.

If you already treat TypeScript as a hard gate, the TypeScript 7 upgrade notes and the typescript-eslint 8.71 enum assignment fix are the adjacent tooling checks.

Is +69 ms enough to notice?

On this fixture, no. Checker added about 3.5% to wall time versus plain Vite. Vite's own "built in" line moved from about 1.75 s to 1.80 s. A standalone tsc --noEmit finished in 985 ms, so if your pipeline already runs tsc in parallel with Vite, duplicating the work inside the plugin is optional rather than required.

Where checker still helps: one command, one exit code, and the same typescript config the editor uses, without wiring a second CI job. Where a separate tsc job is better: you want typecheck to fail before the slower bundle starts, or you share one tsc -b across several packages.

Should you enable vite-plugin-checker on build?

Situation	My pick
No tsc --noEmit in CI today	Enable checker with enableBuild
CI already fails on tsc	Optional; keep tsc, skip enableBuild
Library publish where types are the product	Prefer explicit tsc / api-extractor
Dev-only overlay, ship anyway	checker in serve, not enableBuild
Lint-format gate already covers types via Biome or oxlint typed rules	Re-check; see Biome vs ESLint+Prettier and oxlint vs ESLint​

Bottom line: plain Vite shipped my broken module three times; checker stopped it for about 69 ms on a clean 122-file app. Who should not bother: teams whose CI already fails on tsc --noEmit before deploy. For nearby Vite release behavior, see the Vite 8.3.2 renderBuiltUrl notes.

How this was made: I reused a 122-file React+Vite fixture on the ShopperCove test box, timed interleaved plain and checker builds, injected one type error for a fail/pass matrix, and kept the JSON; the write-up was drafted with AI help and checked against that output.

Sources

• https://github.com/fi3ework/vite-plugin-checker
• https://www.npmjs.com/package/vite-plugin-checker
• https://vite.dev/guide/build.html
• https://www.typescriptlang.org/docs/handbook/compiler-options.html
• https://github.com/vitejs/vite

Related

• https://www.shoppercove.com/blog/typescript-7-should-you-upgrade
• https://www.shoppercove.com/blog/typescript-eslint-8-71-no-unsafe-enum-assignment-october-2026
• https://www.shoppercove.com/blog/biome-vs-eslint-prettier
• https://www.shoppercove.com/blog/oxlint-vs-eslint
• https://www.shoppercove.com/blog/vite-8-3-2-renderbuilturl-bundled-dev-sourcemaps-october-2026
• https://www.shoppercove.com/blog/vite-plus-1-0-unified-toolchain-october-2026
• https://www.shoppercove.com/blog/knip-vs-depcheck
• https://www.shoppercove.com/blog/dprint-vs-prettier