By ByteBot
VoidZero shipped Vite+ beta, and it does something JavaScript has been failing at for a decade: unify the toolchain. Install vite-plus, run vp dev, and your dev server is up. Run vp check and it formats, lints, and type-checks in a single pass. Run vp build and Rolldown handles the production bundle. No .eslintrc, no .prettierrc, no vitest.config.ts, no turbo.json. One config file. One CLI.
This is not a minor release. Vite+ is the most credible attempt yet at giving JavaScript the kind of integrated toolchain that Rust developers take for granted with Cargo, and Python developers now have with uv.
What vp Actually Does
Vite+ ships in two parts: vp, a global CLI, and vite-plus, the local package installed per project. Run npm i vite-plus to get started, or npm create vite-plus to scaffold from scratch.
The vp command covers the full development lifecycle:
vp dev— hot-reloading dev server powered by Vite 8vp check— runs Oxfmt (formatting), Oxlint (linting), and type-checking in one parallelized passvp test— runs your test suite via Vitestvp build— Vite + Rolldown production buildvp pack— library bundling via tsdownvp run— cache-aware monorepo task runnervp env— manage Node.js runtime versionsvp install— dependency management
That last two are the ones that often get overlooked. Vite+ is not just a build tool — it is also managing your runtime and package dependencies. The intent is to be the single entry point for everything in a project.
The Performance Case Is Real
Vite+’s performance gains come from a shared foundation. Rolldown, Oxlint, and Oxfmt all use Oxc — VoidZero’s Rust-based JavaScript compiler — as a common parsing layer. When vp check runs, the AST is built once and reused across formatting, linting, and type information. Structurally faster, not just incrementally so.
- Oxlint: 50–100x faster than ESLint, with 600+ compatible rules; used in production by Shopify and Airbnb
- Oxfmt: 36x faster than Prettier; passes 100% of Prettier’s JavaScript and TypeScript conformance tests
- Rolldown: some projects see production build times drop from 46 seconds to 6 seconds
These are not synthetic benchmarks on contrived inputs. Real projects with real codebases are seeing these improvements. If your CI pipeline currently spends meaningful time on ESLint and Prettier, switching pays for the migration effort quickly.
The JavaScript Ecosystem Finally Has Its Cargo Moment
Evan You said it directly: Vite+ is meant to do for JavaScript what Cargo does for Rust. That framing matters. Cargo is not just a package manager — it is a unified entry point for building, testing, documenting, publishing, and benchmarking Rust code. Python got its version of this with uv. Go has had it built-in from the start.
JavaScript has historically lacked an official, unified tool. The result: every project configures its own stack from scratch, version conflicts between ESLint, Prettier, Vitest, TypeScript, and package managers are a recurring source of CI failures, and onboarding a new developer means learning the configuration archaeology of that particular repo.
Vite+ is backed by Cloudflare (through VoidZero), MIT-licensed, and framework-agnostic. It is not a community experiment that might go unmaintained. That backing matters for adoption decisions.
Who Should Switch Now, and Who Should Wait
The honest answer is that Vite+ beta is ready for some projects and not others.
Good candidates for early adoption:
- New projects with no existing config debt
- Standard Vite + TypeScript projects with conventional ESLint/Prettier setups
- Teams spending real engineering time on lint config conflicts
Wait for 1.0 if your project depends on:
- Template linting for Vue, Svelte, or Angular — Oxlint does not yet support these
- Type-aware ESLint rules — not yet in Oxlint
- Remote caching for CI —
vp runhas local caching only; no Turborepo Remote Cache equivalent yet - Heavy custom Babel or webpack configurations — migration is painful for non-standard setups
The 1.0 roadmap includes remote caching, a setup-vp action for GitHub Actions and GitLab CI, and Vue/Svelte template linting. These are real missing features, not wishlist items. Check the official beta announcement and the GitHub repository for the current status before committing to a migration.
The Bottom Line
Vite+ beta is the most complete attempt at a unified JavaScript toolchain anyone has shipped. The performance improvements from the Oxc-based stack are genuine. The adoption signal — 1,300 public repositories, Laravel starter kits dropping ESLint in favor of Vite+ — is real. The getting started guide is short enough to run through in an afternoon.
Start a new project today with Vite+ and you will likely not regret it. For existing projects, migration to 1.0 is the better bet — especially if you rely on template linting or type-aware rules. But start paying attention now. The JavaScript toolchain story is finally changing, and this is what that looks like.
