I did not expect this...

Vit Plus—an open-source, MIT-licensed alpha of the previously closed-source “V+” toolchain—lands as a unified workflow for modern web development centered on Vit. The pitch is straightforward: collapse the scattered pieces of project management (package/dependency handling, environment setup, testing, scaffolding, bundling, linting, formatting) into one cohesive tool so teams stop juggling fast-changing configs and CLIs. That matters because the ecosystem is already converging around Vit and its “Void Zero” ecosystem, and V+ aims to make the rest of the toolchain feel equally centralized.

The most compelling part is the live migration and performance check. The setup experience includes node version management via an NVM/FNM-style workflow, plus fast code quality commands. In practice, VP check scans and auto-fixes formatting issues across ~15,000 lines in about 332 milliseconds, with formatting and linting reported in the few-hundred-millisecond range (and bun run lint around 0.19 seconds user time). The workflow also introduces V+ “agents” configuration via agent MD files, pre-commit hooks for lint/type/format, and a VP env/doctor flow to wire node version control into shells and editor environments.

Migrating an existing project reveals both the promise and the friction. The migration flow can switch package managers (bun to PNPM) and update scripts, but it exposes gaps: bun support is explicitly rejected during migration, and some orchestration behavior around scripts becomes confusing—especially when custom dev commands are hijacked or when VP rundev doesn’t honor existing package.json script precedence the way bun users expect. A separate issue appears with TanStack Start compatibility: the project initially breaks due to mismatched TanStack package versions, and the fix ends up being a dependency/version alignment plus a clean reinstall rather than a single “run this command” solution.

Despite those rough edges, the build-time results are encouraging. A TanStack Start app that previously built in roughly 28 seconds drops to about 22 seconds after the migration, with the caveat that PNPM installs can be slower and that cloud/deployment overhead still exists. Under the hood, V+ introduces V Tasks, a Rust-based task runner that fingerprints dependency-aware execution, splits multi-command scripts into cached subtasks, and provides a PNPM-like interface via VP run.

The overall verdict is mixed: V+ feels like a serious attempt to centralize the developer experience and reduce decision fatigue, and the speed numbers are real. But alpha-stage roughness shows up in agent MD bloat, missing bun support, script/namespace quirks, and framework edge cases—enough that the narrator doesn’t yet plan to use V+ for all projects. Still, with V+ now open-source and actively iterating, the direction toward one toolchain for the full stack (paired with Void’s broader deployment ambitions) is framed as genuinely exciting, even if not ready to replace established workflows today.