Vite+ 1.0 folds seven JS tools into one command. Here's when that trade pays off.

VoidZero shipped Vite+ 1.0 on September 28, the same day Cloudflare ran its Birthday Week. The pitch is simple: one command, vp, and one vite.config.ts, in place of the pile of tools a normal JavaScript project drags around. A single vite-plus dependency stands in for Vite, Vitest, a linter, a formatter, a Git hook runner, a task runner, and a Node version manager. The commands mean the same thing in every repo: vp dev, vp check, vp test, vp build, vp run. The release is MIT licensed, closing in on two million weekly downloads, and already pulled into more than 2,600 public repositories.

Under the hood it bundles Vite 8, Vitest 5, Rolldown, Oxlint, and Oxfmt, with task caching built in. The linter and formatter are written in Rust, so the checks are quick. VoidZero's own numbers put Oxlint at 50 to 100 times faster than ESLint and Oxfmt up to 30 times faster than Prettier. Vitest 5 is up to 50% faster than Vitest 4, and the Oxc React Compiler runs about 10 times faster than the Babel plugin it replaces. Cloudflare, which now owns VoidZero, framed the speed work around a point worth sitting with: coding agents sit idle while your toolchain grinds, so once inference gets quick, type-checking and linting become the bottleneck.

Here's our honest read. The win is real, and it isn't mainly about the typing you save.

What it actually removes is drift

When we build cloud-native apps for enterprise clients, the slow leak is never one broken tool. It's the gap between tools. The ESLint version on a developer's laptop that isn't the one in CI. The Prettier config that formats differently on two machines. The Node version nobody pinned. Those are small problems, and small problems repeated across a dozen repositories and a few hundred builds get expensive. Vite+ tests its stack as one unit and bumps it as one unit. That's the part that pays off.

The same property is the catch, so go in with eyes open. You upgrade when Vite+ upgrades. You trade a cluster of configs you control for one vendor's defaults. For a new project, that's an easy yes. For a settled codebase with a carefully tuned ESLint ruleset, the real question is whether Oxlint covers the rules you depend on, and nothing in the launch answers that for your specific setup.

What we'd tell a team this week

• Starting something new? Run vp create and skip the week you'd otherwise spend wiring up lint, format, test, and CI. The defaults are sane.
• Have an existing project? Don't rip anything out mid-sprint. Run vp migrate on a branch. It prints its plan before it touches a file, so diff that plan, run your full test suite against it, and only then decide.
• Pin the vite-plus version and let CI, not individual laptops, be the source of truth for the toolchain. That one habit clears out most of the "works on my machine" tickets.

The security angle people are missing

One dependency replacing seven is a smaller attack surface and a shorter audit. During our pentesting engagements and dependency reviews, the long tail of transitive dev dependencies is a recurring soft spot: unmaintained plugins, abandoned formatters, a Git hook package nobody has opened in three years. Consolidating onto one reviewed, well-funded toolchain helps here, as long as you treat that single dependency as critical and keep it patched. Concentration cuts both ways: a bug in the one thing everyone now depends on reaches everyone at once.

The instinct carries past the web, too. In our native iOS and Android work the pain has the same shape even when the tools differ. The gap between the toolchain on a developer's machine and the one on the build server is where flaky builds come from. A toolchain that pins itself end to end is the right direction whatever the platform.

One caution on the Cloudflare framing. The "make your agents faster" story is good marketing and partly true, but it's early. Bundled Dev, the mode built with help from Cloudflare's own dashboard team, is still behind an experimental flag and not released. Treat the agent-speed claims as a reason to watch this closely, not a reason to re-platform today.

If keeping toolchains and CI consistent across a growing set of repositories sounds familiar, let's talk.