Vite+ 1.0 (28 Sep 2026): one vp CLI for the frontend toolchain

On 28 September 2026, VoidZero announced Vite+ 1.0—a stable, MIT-licensed toolchain that wraps Vite, Vitest, Oxlint, Oxfmt, Rolldown, tsdown, and Vite Task behind a single vp command and one vite.config.ts. ShopperCove did not install vp on a production client site or run vp migrate for this note. The facts below come from the official Announcing Vite+ 1.0 post, the Vite+ Getting Started guide, and the vite-plus npm package (version 1.0.0, updated 28 Sep 2026), all read on 5 October 2026. This is not a security exploit guide and not a hands-on migration log.

There is no affiliate link in this article.

Related links

• 01shoppercove.com/blog/nextjs-15-lts-end-of-support-october-2026
• 02shoppercove.com/blog/sveltekit-3-migration-checklist-october-2026
• 03shoppercove.com/blog/react-19-3-view-transitions-fragment-refs-2026

What Vite+ is (and is not)

From the 1.0 announcement and Getting Started:

• Is: a unified entry point for web tooling. One dependency (vite-plus) and one global/local CLI (vp) cover create, install, dev, check, test, build, pack, and monorepo task caching.
• Is not: a new framework, a package-manager replacement by itself, or a drop-in rename of Vite alone. The announce says it is “definitely not a replacement for Vite”—it ties tools you already use into one tested stack.
• License: MIT; framework-agnostic (React, Vue, Node CLIs, monorepos—even projects that do not use Vite for the app layer).

The announce’s headline install path is curl -fsSL https://vite.plus | bash, then vp create or vp migrate. The guide also documents Windows (irm https://vite.plus/ps1 | iex) and a project-local path via pnpm dlx --package=vite-plus@1.0.0 / npx --package=vite-plus@1.0.0 so you are not forced to install the global CLI first.

Core commands freelancers will actually use

The announce lists nine everyday commands; the guide expands the same set:

CommandRole (per VoidZero docs)vp createScaffold app, library, or monorepovp migrateAdopt Vite+ in an existing project (shows a plan before changing files)vp installInstall deps with the project’s package managervp devDev server (Vite 8 + Rolldown)vp checkFormat + lint + type-check in one pass (Oxfmt / Oxlint)vp testUnit / component / browser tests (Vitest)vp buildProduction app buildsvp packLibrary builds / standalone binaries (tsdown)vp runMonorepo-aware task runner with caching

Config lives in one root vite.config.ts via defineConfig from vite-plus, with blocks for Vite, test, lint, fmt, run, and staged. Built-ins (vp dev, vp test) are not the same as vp run dev / vp run test, which run package.json scripts—keep that distinction when you rewrite CI.

What changed since beta (announce highlights)

As of the 1.0 post:

• setup-vp for GitLab CI/CD (alongside the existing GitHub Action).
• Broader vp migrate targets (including tsup migrations).
• Homebrew and a Docker image.
• vp toolchain (exact tool versions) and vp env doctor.
• vp hooks / vp staged for Git hooks on staged files.
• Under the hood: Vitest 5 stable, Vite 8.1 with experimental Bundled Dev Mode, Oxc native React Compiler support (announce claims ~10× vs the Babel plugin it replaces).

npm’s vite-plus@1.0.0 page (read 5 Oct 2026) listed weekly downloads around 2.58 million and pinned Vitest 5.0.1 / Oxlint 1.85.0 / Oxfmt 0.70.0 as dependencies—numbers drift; treat the registry as the live pin source.

Freelancer / client-site checklist (read-only)

1. Inventory tooling first. Note which repos still juggle separate Vite, Vitest, ESLint, Prettier, tsup/tsdown, and turbo/nx scripts. Vite+ is aimed at that glue cost, not at rewriting app code.
2. Prefer a greenfield smoke test. vp create on a throwaway folder before touching a paying client monorepo.
3. For existing apps, read the migrate guides before running anything. Official paths: viteplus.dev/guide/migrate and the announce’s warning that large projects may need follow-up after vp migrate shows its plan.
4. Prerequisites the docs call out: upstream Vite 8+ and Vitest 4.1+ before migrating; do not install vite-plus or jump Vitest to the bundled major until the migrator has seen the old graph (per the guide’s agent/migrate instructions).
5. CI: if you adopt globally, pin voidzero-dev/setup-vp to an exact release or commit SHA—the npm README says the floating v1 tag no longer receives updates.
6. Pair with October runtime pressure. If the same sprint also covers Node 26 Active LTS (28 Oct) or Next.js 15 Maintenance LTS end (21 Oct), keep those windows separate from a Vite+ migration so you can attribute breakages.

ShopperCove did not run these commands on a live storefront. Match VoidZero’s docs and your hosting constraints.

Bottom line

Vite+ 1.0 (28 Sep 2026) is VoidZero’s stable “one CLI, one config” stack for Vite 8 / Vitest 5 / Oxc / Rolldown / tsdown. Start from the announce and Getting Started; use vp migrate only after reading the migrate guide on a non-production branch.

Sources

• 01voidzero.dev/posts/announcing-vite-plus-1-0
• 02viteplus.dev/guide
• 03npmjs.com/package/vite-plus
• 04viteplus.dev/guide/migrate