# vp build vs vite build: Key Differences in the Vite‑Plus Monorepo Tool > Explore vp build vs vite build differences. Discover how vp build uses Rolldown for faster Rust-based builds in monorepos, optimizing your Vite Plus workflow. - Repository: [VoidZero/vite-plus](https://github.com/voidzero-dev/vite-plus) - Tags: deep-dive - Published: 2026-03-16 --- **`vp build` is a Rust-based CLI wrapper that replaces Rollup with Rolldown for faster production builds while adding package-manager awareness and workspace support, though it deliberately skips Vite‑Plus's task-graph caching layer.** The `vp build` command is the production build entry point for **Vite‑Plus** (`voidzero-dev/vite-plus`), a monorepo-aware toolchain that wraps Vite's core functionality. While it ultimately delegates to Vite's production pipeline, the surrounding architecture, bundler substitution, and workspace integration create significant behavioral differences compared to running `vite build` directly in a standard project. ## Entry Point and CLI Architecture The command originates in the **Vite‑Plus CLI** rather than the standard Vite binary. In [`packages/cli/binding/src/cli.rs`](https://github.com/voidzero-dev/vite-plus/blob/main/packages/cli/binding/src/cli.rs), the build subcommand resolves through `vite_command::build_command` and launches via the shared `run_command` helper defined in [`crates/vite_command/src/lib.rs`](https://github.com/voidzero-dev/vite-plus/blob/main/crates/vite_command/src/lib.rs) (lines 91–106). This contrasts with standard Vite, which executes directly from `node_modules/.bin/vite`. The command registration happens in [`crates/vite_global_cli/src/command_picker.rs`](https://github.com/voidzero-dev/vite-plus/blob/main/crates/vite_global_cli/src/command_picker.rs) (lines 79–80), where the label "build" maps to the internal command dispatcher. This global CLI layer provides the foundation for Vite‑Plus's monorepo orchestration before the actual Vite binary is invoked. ## Bundler Difference: Rolldown vs Rollup The most significant technical divergence lies in the bundler implementation. **`vp build`** uses **Rolldown**, a Rust-based bundler that replaces Rollup. According to the documentation in [`docs/guide/build.md`](https://github.com/voidzero-dev/vite-plus/blob/main/docs/guide/build.md) (lines 7–8), Vite‑Plus pins Vite 8 and substitutes the JavaScript-based Rollup with Rolldown to achieve faster build times. **Standard `vite build`** uses the **Rollup** bundler bundled with the standard Vite distribution, which remains the default for non-Vite‑Plus environments. This architectural choice means that while the build output remains compatible, the performance characteristics and internal module graph handling differ substantially between the two approaches. ## Package Manager and Workspace Awareness Before invoking the Vite binary, the CLI ensures proper environment setup. In [`packages/cli/binding/src/cli.rs`](https://github.com/voidzero-dev/vite-plus/blob/main/packages/cli/binding/src/cli.rs) (line 462), the code calls `vite_install::PackageManager::builder(cwd).build_with_default().await?` to detect and validate the correct package manager for the monorepo context. The command respects the workspace layout defined in the monorepo configuration, ensuring that builds execute against the correct package boundaries. Standard `vite build` assumes the user has manually managed the package manager context and executes against the locally installed Vite binary without additional workspace validation. ## Caching and Task Graph Behavior Despite Vite‑Plus's sophisticated task-graph capabilities, the build command deliberately opts out of them. A comment in [`packages/cli/binding/src/cli.rs`](https://github.com/voidzero-dev/vite-plus/blob/main/packages/cli/binding/src/cli.rs) (lines 987–989) explicitly states: "No caching, no task graph, no dependency resolution." This means `vp build` executes as a standalone command without leveraging Vite‑Plus's incremental caching or dependency resolution layers, even though the broader toolchain supports these features. Standard `vite build` similarly lacks built-in caching, though external plugins (such as `vite-plugin-react`) may implement their own cache layers that function normally in both environments. ## Command Flags and Script Execution Both commands accept identical Vite-specific flags, but their execution contexts differ. **Flag Handling:** `vp build` mirrors standard Vite flags (`--watch`, `--sourcemap`, etc.) by passing them directly to the underlying Vite binary, as documented in [`docs/guide/build.md`](https://github.com/voidzero-dev/vite-plus/blob/main/docs/guide/build.md) (lines 14–19). The wrapper does not intercept or transform these arguments. **Script Execution:** `vp build` **always** executes Vite's internal build pipeline. To run a user-defined [`package.json`](https://github.com/voidzero-dev/vite-plus/blob/main/package.json) build script (such as `"build": "vite build --emptyOutDir"`), you must use `vp run build` instead. This distinction is documented in [`docs/guide/build.md`](https://github.com/voidzero-dev/vite-plus/blob/main/docs/guide/build.md) (lines 9–11), where the guide clarifies that `vp run` invokes the task runner while `vp build` invokes the compiler directly. ```bash # Build using Vite‑Plus (Rolldown bundler) vp build vp build --watch vp build --sourcemap # Run custom package.json script via task runner vp run build ``` ```bash # Standard Vite build (Rollup bundler) vite build vite build --watch ``` ## Summary - **`vp build`** executes through the Vite‑Plus Rust CLI ([`packages/cli/binding/src/cli.rs`](https://github.com/voidzero-dev/vite-plus/blob/main/packages/cli/binding/src/cli.rs)) rather than the standard Vite binary. - The command uses **Rolldown** instead of Rollup, providing faster bundling performance for production builds. - Package manager detection and workspace layout validation occur automatically before build execution. - Despite Vite‑Plus's caching infrastructure, `vp build` deliberately disables task-graph and caching layers for production builds. - To execute custom [`package.json`](https://github.com/voidzero-dev/vite-plus/blob/main/package.json) build scripts, use `vp run build` rather than `vp build`. ## Frequently Asked Questions ### Does vp build support the same CLI flags as vite build? Yes. According to the source code in [`docs/guide/build.md`](https://github.com/voidzero-dev/vite-plus/blob/main/docs/guide/build.md), `vp build` passes flags such as `--watch` and `--sourcemap` directly to the underlying Vite binary without transformation. The wrapper layer handles package-manager setup and binary resolution, but flag propagation remains transparent. ### Why does vp build not use Vite‑Plus's caching system? The implementation in [`packages/cli/binding/src/cli.rs`](https://github.com/voidzero-dev/vite-plus/blob/main/packages/cli/binding/src/cli.rs) (lines 987–989) explicitly disables caching, task graphs, and dependency resolution for production builds. This design choice treats production builds as deterministic, stateless operations that should produce identical outputs regardless of incremental cache state, ensuring consistency across CI/CD environments. ### Can I use vp build in a non-monorepo project? While technically possible, `vp build` is designed specifically for the Vite‑Plus monorepo context. The command performs package-manager validation and workspace detection that may add unnecessary overhead in single-package projects. Standard `vite build` remains the recommended approach for non-monorepo Vite applications. ### What is the difference between vp build and vp run build? `vp build` invokes Vite's internal production compiler directly (using Rolldown), while `vp run build` executes the `build` script defined in your [`package.json`](https://github.com/voidzero-dev/vite-plus/blob/main/package.json) through the Vite‑Plus task runner. If your project defines custom build logic (such as `vite build --emptyOutDir`), you must use `vp run build` to execute that script rather than the default compiler command.