Announcing Vite+ 1.0

TL;DR: Vite+ 1.0 is out, stable, MIT licensed, and about to reach two million weekly downloads. A single command, vp, manages your Node.js runtime, package manager, and frontend toolchain. Install it with curl -fsSL https://vite.plus | bash, then run vp create for a new project or vp migrate to migrate your existing one.

Today we are releasing Vite+ 1.0, the unified toolchain for the web.

Vite+ is a single entry point to web development, built by the team behind Vite, Vitest, Rolldown, and Oxc.

It is neither a framework, nor a package manager and definitely not a replacement for Vite. Instead, Vite+ ties the tools you already use into one tested stack with a single config file and a consistent set of commands.

Vite+ is free, open source under MIT, and framework-agnostic. Whether you ship a React app, a Vue component library, a Node CLI, or a 400-package monorepo, the commands stay the same. Your project does not even have to use Vite in the first place!

The cost of assembling your own toolchain ​

Starting a web project means a lot of choices to make before even starting to write your first line of code:

• picking a runtime,
• choosing a package manager,
• deciding on a dev server,
• setting up a linter, a formatter, a test runner, a bundler, you name it.

Each one brings its own config files, release cadence, commands, and its own upgrade guide. And that matters for you at least twice. First when you pick the tool stack (or get onboarded to it), then every time things drift apart:

• the linter disagrees with the formatter,
• CI runs different commands than you do locally,
• one repo is two majors behind another,
• and the person who originally set it up is on vacation.

Teams with more than a handful of repositories usually end up building internal scripts to paper over this, which then need their own maintainers. But instead of maintaining a tool stack, you often just want to ship features.

What Vite+ offers ​

Nine commands cover the local development cycle:

One vite.config.ts at the project root configures all of them. Run vp with no arguments to get an interactive prompt instead.

What changes in practice ​

You stop maintaining tooling. A single vite-plus dependency replaces a cluster of dependencies (e.g., vite, vitest, eslint, prettier, tsup, turbo) and their plugins and configs. Upgrades become one version bump that is tested as a unit before releasing.

You feel at home in every repo. The built-in vp commands mean the same thing everywhere, and anything a project defines itself runs through vpr <script>. Helpful for your newly onboarded colleagues and agents.

Faster feedback. The tools underneath are written in Rust: Oxlint runs 50x to 100x faster than ESLint, Oxfmt up to 30x faster than Prettier, and Vite 8 builds significantly faster thanks to Rolldown.

CI gets faster. vp run records which files, arguments, and environment variables a task actually used, so a cached task replays instantly if it is unchanged. With setup-vp, the Node setup, package manager setup, and dependency cache steps in your workflow collapse into one action.

No lock-in. Continue using your favorite Vite plugins and package manager and make use of vp run's caching for arbitrary scripts, not only built-in commands.

What changed since the beta ​

A lot happened since we shipped the beta in July:

• setup-vp for GitLab CI/CD, alongside the existing GitHub Action.
• More migration targets. vp migrate now handles tsup migrations and more edge cases are resolved.
• Homebrew and a Docker image are available.
• vp toolchain reports the exact version of every tool Vite+ provides, and vp env doctor explains runtime and package manager resolution when it goes wrong.
• vp hooks sets up, enables, and disables Git hooks, with vp staged running checks on staged files only.
• Compatibility work across the Vite plugin and framework ecosystem.

The tools Vite+ relies on were upgraded too. Vitest 5 is stable, Vite 8.1 shipped the experimental Bundled Dev Mode, and Oxc gained native React Compiler support, which makes the compiler 10x faster than the Babel plugin it replaces.

Who is using it ​

Vite+ is closing in on two million weekly downloads, and more than 2,600 public repositories depend on vite-plus today, not counting private projects and global installs. Tiptap replaced its separate Vite, Vitest, tsup, and Oxc setup with Vite+, and adoption spans project types:

• Dify, an open-source platform for building LLM apps
• vinext, a Next.js-compatible framework built on Vite
• BlockNote, a Notion-style rich text editor for React
• Inkline, a component library shipping to Vue, React, Svelte, Angular, Solid, Qwik, and Astro
• npmx, an open-source npm registry browser built on Nuxt
• hono, a small, simple, and fast web framework.

Get started ​

Install vp:

curl -fsSL https://vite.plus | bash

irm https://vite.plus/ps1 | iex

Open a new shell, then start a project:

vp create

Or adopt Vite+ in a project you already have:

vp migrate

vp migrate shows its plan before changing files, and large projects might need a follow-up. Read the migration guide first if the project is in production.

Working with a coding agent? Use our migration prompt!

What's next ​

Vite+ reached 1.0 but is far from feature-complete. Functionality such as remote caching, deeper monorepo diagnostics, vp release, and vp docs are planned for future versions.

Acknowledgements ​

Vite+ is built in the open by a growing international core team together with the community. Half of our core team grew out of the community itself, and Vite+ would be a smaller and slower project without the reviews, bugfixes, and features shipped by:

• kazupon
• ubugeeei
• nekomoyi
• Stefan Haas
• naokihaba
• JongKyung Lee
• Liang
• Yii

Thank you to everyone who ran the alpha and beta on real projects, filed bug reports, and sent pull requests. Vite+ exists because Vite, Vitest, Rolldown, Oxc, and tsdown exist, and because the people maintaining them keep making them better.

Connect with us ​

• Documentation: viteplus.dev
• Discord: Step into the Void
• GitHub: Star the repo, open issues, send pull requests
• X and Bluesky: @voidzerodev and @voidzero.dev
• Newsletter: Subscribe for future announcements