💬 Vite plugin that provide checks of TypeScript, ESLint, vue-tsc, Stylelint and more.
1.2k
Stars
134
Forks
101
Open issues
30
Contributors
AI Analysis
A Vite plugin that runs TypeScript, vue-tsc, ESLint, Biome, and Stylelint checks in worker threads during development. It serves teams building Vue and React applications who need integrated, non-blocking linting and type checking in their build pipeline. Best suited for developers using Vite in modern web projects; not for non-Vite workflows or projects that don't use these specific linters.
Inferred from signals mentioned in the README (tests, CI, type safety) — not a review of the actual code.
AI's overall editorial judgment — not an average of the bars above, can weigh other factors too.
Vite plugin that runs linting and type checks in worker threads during development
vite-plugin-checker integrates TypeScript, ESLint, vue-tsc, Biome, and Stylelint into Vite's dev server, running checks in background worker threads to avoid blocking the dev loop. Built for developers using Vite who want integrated linting feedback without CLI context-switching. Adoption appears moderate within the Vue/Vite ecosystem; not a dominant standard but well-established in its niche.
Created March 2021 during early Vite adoption. Emerged to solve a specific Vite dev experience gap: lack of built-in linting integration. Evolved from focusing on TypeScript/vue-tsc to supporting multiple checkers (ESLint, Stylelint, Biome) as the ecosystem expanded.
Steady accumulation (~1,200 stars over 5 years) suggests stable, niche adoption rather than explosive growth. Last 7 days shows only 1 star gain, indicating mature equilibrium rather than declining interest. Most growth likely occurred 2021–2023 as Vite became mainstream. Current activity (last push June 2026) shows active maintenance but at a sustainable, low-velocity cadence typical of mature, solved-problem tools.
Adoption not verified through README. No case studies, company endorsements, or download metrics mentioned. Presence of StackBlitz examples suggests some community engagement, but scope of real-world production adoption is unclear. Comparable to similar Vite plugins in star count but without explicit production telemetry.
Likely uses Vite's plugin API to hook into dev server lifecycle. Appears to spawn worker threads for type/lint checks to prevent main thread blocking. Based on README, supports modular checker configuration (TypeScript, ESLint, vue-tsc, Biome, Stylelint as separate, composable checks). Actual implementation architecture not verifiable from README alone.
Not documented in README. No test strategy, CI pipeline, or coverage metrics mentioned.
Recent push (June 22, 2026) indicates active maintenance as of current date. Project is 5+ years old and still receiving updates, suggesting long-term stewardship. Lack of high velocity (1 star/week) likely reflects maturity and solved scope rather than abandonment.
ADOPT IF: you are using Vite with TypeScript/Vue and want integrated type and linting feedback in the dev server without context-switching to CLI, and you tolerate potential performance overhead from background checks. AVOID IF: you need production-grade error handling, extensive test coverage documentation, or strong adoption evidence in your specific framework; or if your team already has reliable pre-commit/CI linting and considers dev-time checks redundant. MONITOR IF: you are considering it for a new Vite project and want to verify recent adoption trends or maintenance continuity in your specific ecosystem (Vue vs. React vs. generic Vite).
Independent dimensions
Mainstream potential
4/10
Technical importance
5/10
Adoption evidence
3/10
- Test coverage not documented; actual code quality and edge case handling cannot be verified from README.
- Worker thread overhead could slow dev experience on large projects if checks are expensive; tradeoff not explicitly discussed in README.
- Adoption not quantified; no evidence of production scale usage or known users; adoption may be limited to tutorial/small-project adoption.
- Dependency on multiple external checkers (TypeScript, ESLint, vue-tsc, Biome, Stylelint); breaking changes in those tools could cascade; maintenance burden grows with each added checker.
- Niche within niche: benefits primarily Vue developers using Vite; value proposition for React or generic JS is less clear.
Likely to remain a stable, niche tool within the Vite + Vue ecosystem. May experience modest growth if Vite adoption accelerates, but unlikely to become a default Vite standard because linting philosophy is opinionated (some teams prefer CI-only checks). May be superseded by tighter native Vite integration or community consolidation around other plugin frameworks, but current maintenance suggests multi-year runway.
Newsletter
Get analyses like this every Monday
Free weekly digest of the most interesting open-source discoveries.
Languages
Information
- Language
- TypeScript
- License
- MIT
- Last updated
- 2d ago
- Created
- 64mo ago
- Analyzed with
- anthropic/claude-haiku-4-5
Stars over time
Contributors over time
Top 100 contributors only — repos with more will plateau at 100.
Open issues
How to use this tool with NX?
0.14.3 missing dist/@runtime/main.js from npm package (breaks dev server)
Biome diagnostics are missing on Windows when JSON reporter emits unescaped backslashes in file paths
Overlay isn't shown despite TypeScript errors
Similar repos
antfu-collective/vite-plugin-inspect
vite-plugin-inspect is a debugging tool for Vite plugin developers that...
vitejs/vite-plugin-react
Vite Plugin React is the official, all-in-one Vite plugin for React projects,...
sveltejs/vite-plugin-svelte
Official Svelte plugin for Vite, enabling seamless integration of Svelte...
vuejs/eslint-plugin-vue
The official ESLint plugin for Vue.js that enforces linting rules specific to...
| Repository | Stars | Week Δ | Language | Score | Updated |
|---|---|---|---|---|---|
|
fi3ework/vite-plugin-checker
this
|
1.2k | +2 | TypeScript | 7/10 | 2d ago |
|
antfu-collective/vite-plugin-inspect
|
1.7k | — | TypeScript | 8/10 | 3w ago |
|
vitejs/vite-plugin-react
|
1.1k | — | TypeScript | 8/10 | 4d ago |
|
sveltejs/vite-plugin-svelte
|
1k | — | JavaScript | 8/10 | 2d ago |
|
vuejs/eslint-plugin-vue
|
4.6k | — | TypeScript | 8/10 | 7d ago |
|
vitejs/vite
|
82k | — | TypeScript | 9/10 | 2h ago |
Higher star count (1,679 vs 1,232); vite-plugin-inspect focuses on introspection/debugging of Vite modules, while vite-plugin-checker focuses on code quality. Different problem domains; not direct competitors.
IDE extensions run checks natively in editor; vite-plugin-checker integrates into dev server console. Trade-off: plugin provides unified feedback in Vite console and CI consistency; IDE extensions offer real-time in-editor warnings. Complementary rather than replacements.
Traditional approach: run Vitest, ESLint, TypeScript as separate CLI commands. vite-plugin-checker unifies some checks into dev loop. Vitest (16k+ stars) dominates testing; this plugin addresses the linting-in-dev-loop gap, not the testing gap.
Vite itself does not bundle linting out-of-the-box; developers must compose plugins. vite-plugin-checker is one consolidation strategy; others build custom solutions or use multiple specialized plugins.
Pre-commit approach catches issues before commit; vite-plugin-checker catches issues during dev. Orthogonal strategies; often used together for defense-in-depth.
