VoidZero's `vp` CLI reaches stable 1.0 with nearly two million weekly downloads, consolidating the modern JavaScript stack.
VoidZero released Vite+ 1.0 on September 28, 2026 — a unified command-line toolchain that manages Node.js runtimes, package managers, and frontend build pipelines behind a single vp binary. The project is MIT licensed, approaching two million weekly downloads, and already used in more than 2,600 public repositories.
What vp replaces
Modern JavaScript projects often juggle:
- nvm or fnm for Node versions
- npm, pnpm, or yarn for dependencies
- Vite for dev server and builds
- Vitest for testing
- tsup or Rolldown for libraries
- Separate formatters and linters
Vite+ collapses these into one interface:
| Command | Purpose |
|---|---|
vp create | Scaffold apps, libraries, or monorepos |
vp dev | Dev server with HMR via Vite 8 and Rolldown |
vp check | Format, lint, and type-check (Oxfmt, Oxlint) |
vp test | Unit and browser tests via Vitest |
vp build | Production builds |
vp migrate | Migrate existing projects, including tsup setups |
Install globally with:
curl -fsSL https://vite.plus | bash
Why it matters now
Toolchain fragmentation taxes every new hire and CI pipeline. Vite+ follows the success of opinionated frameworks — Next.js, Remix, SvelteKit — but at the meta layer beneath them. Tiptap reportedly replaced a multi-tool setup with Vite+ across its monorepo.
Rolldown integration matters for build performance. As bundlers converge on Rust implementations, a stable orchestration layer prevents each repo from reinventing migration scripts.
Migration considerations
vp migrate handles many tsup and Vite 7 configurations, but teams should:
- Run migration on a branch and diff CI workflows carefully
- Verify native addon compatibility with the Node version
vp envselects - Update documentation so contributors do not mix legacy npm scripts with
vpcommands
Roadmap gaps
VoidZero acknowledges 1.0 is not feature complete. Planned additions include remote caching, vp release, vp docs, and deeper monorepo diagnostics.
Takeaway
JavaScript fatigue often stems from configuration surface area, not language limitations. Vite+ bets that developers will trade slight abstraction for a single blessed path — a familiar trade in exchange for velocity. If your starter template still lists eight devDependencies before application code, evaluate vp create on your next greenfield project.
Comments
Loading comments…