Skip to content
rsdlt.dev
Go back

Vite+ 1.0 Is Out: Should Foambyte Trade Its Toolchain for One Command?

On September 28, VoidZero announced Vite+ 1.0, the team behind Vite, Vitest, Rolldown and Oxc. It’s a single toolchain behind a single command, vp, and a single vite.config.ts.

Foambyte already uses most of the pieces Vite+ packages: Vite for the React app, Vitest for 660+ unit and integration tests, and a pnpm + Turborepo monorepo stitching it all together. So the question isn’t whether Vite+ is interesting. It’s whether swapping our hand-assembled toolchain for one opinionated package is worth it. We’re evaluating that now. This post covers what shipped and where we’ve landed so far.

What Vite+ 1.0 is

Vite+ is a toolchain, not a framework or a package manager, and not a replacement for Vite. One vite-plus dependency replaces a stack of separate tools, each with its own config, release cadence and upgrade path:

CommandWhat it runsReplaces
vp devVite 8 dev server with HMRvite
vp buildVite 8 + Rolldown production buildvite build
vp checkOxlint, Oxfmt and type checkingESLint, Prettier, tsc
vp testVitest (unit, component, browser)vitest
vp packtsdown library builds and binariestsup, rslib and similar
vp runVite Task, a monorepo task runner with cachingTurborepo
vp envNode.js version managementnvm, mise (for Node)
vp installYour package manager of choicen/a, it wraps pnpm/npm/…

There are also vp create for new projects, vp migrate for existing ones (it shows its plan before touching files), vp hooks and vp staged for Git hooks, and vp toolchain to see the exact version of every bundled tool. CI gets a setup-vp action for GitHub Actions and GitLab that combines Node setup, package manager setup and dependency caching into one step.

A few details from the announcement stand out:

How Foambyte’s toolchain looks today

For context, here’s what Vite+ would be replacing:

That’s at least seven tools with seven configs, and every one of them works. That matters for what follows.

Pros and cons

ProsCons
One config, one upgrade path. Vite, Vitest, linting and the task runner ship as one tested set.Turborepo already works. vp run has no remote caching yet, so replacing it is high risk for little gain.
No more Babel for the React Compiler. Oxc compiles it natively, so the frontend build gets faster.Lint parity is unproven. Oxlint has to cover the ESLint rules we rely on, including the React Compiler rule.
Much faster checks. Our AI coding agents run lint and format many times per change, so the speedup adds up.Not everything is Vite. Wrangler still builds the API, and Capacitor still builds the mobile apps.
Familiar tools. Vite and Vitest stay the same, so our 660+ tests shouldn’t need changes.Coupled releases. Every tool upgrades together, so we can’t pin around one tool’s regression.
Fewer dependencies. One vite-plus package replaces several, which means less supply-chain review.Overlap with mise. vp env and mise would both manage Node.
Vendor concentration. The whole toolchain comes from one company, which is now joining Cloudflare.

Takeaways


I’m Rodrigo Santiago, a product leader who builds. I co-founded Foambyte with my brother Diego, a brewmaster who leads the product as CPO, and I designed and built the platform: architecture, frontend, backend, mobile and infrastructure. If you need someone who can own both the product and the code, let’s talk on LinkedIn.


Share this post:

Next Post
How I Use Claude Code on a Production SaaS Without Vibe Coding