explaingit

voidzero-dev/vite-plus

4,600RustAudience · developerComplexity · 2/5LicenseSetup · easy

TLDR

Vite+ bundles a dev server, test runner, linter, formatter, and production bundler into one CLI tool called `vp`, all configured from a single vite.config.ts instead of five separate tool configs.

Mindmap

mindmap
  root((repo))
    What it does
      Unified web toolchain
      Single CLI for all tools
    Bundled tools
      Vite dev server
      Vitest testing
      Oxlint linting
    Commands
      vp dev
      vp check
      vp build
      vp migrate
    Tech stack
      Rust
      TypeScript
    Features
      Monorepo support
      Single config file
Click or tap to explore — scroll the page freely

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

Things people build with this

USE CASE 1

Replace separate Vite, ESLint, Prettier, and Vitest configs with one vite.config.ts and a single CLI

USE CASE 2

Migrate an existing web project to Vite+ using `vp migrate` to consolidate scattered config files

USE CASE 3

Run lint, format checks, and type checks together with one `vp check` command

USE CASE 4

Manage tasks across a monorepo with the built-in task runner via `vp run`

Tech stack

RustTypeScriptViteVitestRolldown

Getting it running

Difficulty · easy Time to first run · 5min

Install with a single curl or PowerShell command, automatically detects your existing package manager.

Free to use, modify, and distribute for any purpose, including commercial use, as long as you keep the copyright notice.

In plain English

Vite+ is a command-line tool that pulls together several separate web development utilities into one package, controlled through a single command called vp. Instead of installing and configuring a build tool, a test runner, a linter, a formatter, and a package manager wrapper separately, Vite+ gives you all of them through one install and one config file. The tools bundled inside include Vite for the development server and frontend builds, Vitest for running tests, Oxlint for code linting, Oxfmt for code formatting, Rolldown for production bundling, and a task runner for monorepo workflows. All of these can be configured from a single vite.config.ts file at the root of your project, rather than maintaining separate config files for each tool. The command list covers the full lifecycle of a web project. You run vp dev to start a local development server, vp check to run formatting, linting, and type checks together, vp test to run your test suite, and vp build to produce a production-ready bundle. There are also commands for managing Node.js versions (vp env), installing packages (vp install), running tasks across a monorepo (vp run), and packaging libraries for publishing to npm. A migration command, vp migrate, can take an existing project with scattered config files and consolidate them into the unified format. Installing it is a single curl or PowerShell command depending on your operating system. It detects which package manager a project already uses (npm, pnpm, or Yarn) and wraps it automatically, so commands like vp add and vp remove work regardless of which package manager is underneath. The project is open-source under the MIT license and comes from the team behind Vite. A GitHub Actions integration is available for running Vite+ in CI pipelines.

Copy-paste prompts

Prompt 1
I just installed Vite+ from voidzero-dev/vite-plus. Show me what the vite.config.ts should look like for a basic React app and how to start the dev server with `vp dev`.
Prompt 2
Using voidzero-dev/vite-plus, walk me through migrating a project that has separate eslint, prettier, and vitest config files into the unified single-file setup.
Prompt 3
I want CI for my voidzero-dev/vite-plus project in GitHub Actions. Show me a workflow YAML that runs `vp check` and `vp test` on every pull request.
Prompt 4
How does `vp build` in voidzero-dev/vite-plus differ from a standard Vite build? What does Rolldown change and when does the difference matter?
Open on GitHub → Explain another repo

← voidzero-dev on gitmyhub — every repo by this author, as a profile.

Verify against the repo before relying on details.