I did not expect this...

TL;DR

Vite Plus (V+) launched as open-source MIT-licensed toolchain unifying package management, linting, and node versioning, but has too many rough edges for production use yet.

Key Points

• 1.V+ is now open-source under MIT license. Void Zero's previously closed-source paid tool Vite Plus launched in alpha as a unified toolchain covering packages, environments, testing, scaffolding, bundling, linting, and formatting.
• 2.Linting speed is genuinely impressive. VP check ran across 15,000 lines of code in 332 milliseconds, with formatting completing in 341ms and linting in 247ms — comparable to bun's 190ms user time.
• 3.Node version management is a standout feature. V+ pins node versions per project via a `.node-version` file, replacing FNM/NVM with a cleaner team-friendly approach that works across different developer environments.
• 4.The auto-generated agents.md files are described as 'actual garbage.' The scaffolded AI context files included irrelevant commands like `create` and `migrate` for already-initialized projects, hurting agent performance — confirmed by Void Zero team as still being refined.
• 5.Bun is not supported, which is a significant gap. Migration command failed with 'unsupported package manager: bun,' frustrating early adopters who are likely the same bleeding-edge developers already using bun — support is reportedly planned.
• 6.VP dev conflicts with custom script commands. Unlike bun's shorthand behavior, V+ requires `vp run dev` to execute package.json scripts, and built-in commands like `vp dev` override custom dev scripts without warning — called out as bad UX that must be fixed before leaving alpha.
• 7.Build time improvement was modest: 28s down to 22s. After migrating a real Tanstack Start app from Vite 7 + bun to V+ + PNPM, build times dropped ~6 seconds, partly attributed to PNPM caching rather than V+ itself.
• 8.Overall verdict: exciting vision, not production-ready. The creator sees V+ as a promising future where one tool replaces 15 others, but personally won't adopt it widely yet due to edge cases, namespace conflicts, and missing bun support.