Vite Plus Goes Open Source—With Sharp Edges Still Showing
Vite Plus launched as open source alpha, promising unified tooling. Early testing reveals impressive speed alongside design choices that may frustrate power users.
Written by AI. Bob Reynolds
March 19, 2026

Photo: Theo - t3․gg / YouTube
Vite Plus arrived last week as an open-source alpha, and the web development community is watching closely. The unified toolchain from Void Zero promises to consolidate the sprawl of tools that modern frontend developers juggle daily—bundling, linting, formatting, testing, environment management—into one cohesive system. It's an ambitious pitch for a field that has historically resisted this kind of consolidation.
Content creator Theo, who runs the t3.gg channel, decided to test Vite Plus live on camera, migrating projects and poking at its boundaries. His half-hour exploration offers a useful window into what works, what doesn't, and where the tension points lie between tool philosophy and developer expectations.
Speed That Actually Matters
The most immediate impression: Vite Plus is fast. Theo's linting and formatting commands across 15,000 lines of code completed in under half a second. The formatting took 341 milliseconds. Linting finished in 247 milliseconds. These aren't marketing benchmark numbers—these were live, practical measurements.
"The fact that it takes under half a second across everything here is insane," Theo noted during testing. "The formatting took 341 milliseconds. The linting took 247 milliseconds. That's absurdity."
For context, his existing Bun-based linting took 0.19 seconds—not dramatically slower, but the point stands that Vite Plus delivers on its performance promises. In an era where developers increasingly rely on pre-commit hooks and continuous checks, milliseconds compound into minutes saved daily.
The Node version management impressed him more than he expected. Vite Plus can pin specific Node versions to projects, making it simpler to maintain different environments across a developer's machine. "I was skeptical of V+ managing my node versions, but they do this right," he said. Coming from someone who maintains major open-source projects, that endorsement carries weight.
The Friction Points
But speed isn't everything. Several design decisions revealed friction between Vite Plus's approach and how experienced developers actually work.
First, the tool doesn't support Bun, the JavaScript runtime that many early adopters have embraced. When Theo tried migrating a Bun project, Vite Plus simply refused: "Unsupported package manager." For a tool targeting cutting-edge developers—the exact demographic likely to experiment with Bun—this creates an awkward gap. Void Zero apparently plans Bun support, but it's not there yet.
The more philosophical issue involves command precedence. Vite Plus implements its own vp dev command that bypasses custom dev scripts defined in package.json. When Theo ran vp dev, it ignored his carefully configured concurrent processes and ran Vite Plus's default instead.
This hit a nerve. "You do know this is the single biggest complaint we have about bun, right?" Theo said, visibly frustrated. "The thing we put in scripts should always take precedent 100% of the time. I know this sounds like a petty hill to die on. This needs to be fixed before you're out of alpha. Hard stop."
He's identifying a pattern: tools that assume they know better than the developer's explicit configuration. Bun does this with its bun test command, which behaves differently than bun run test. Developers who've been burned by that behavior don't want to see it replicated.
The Agents Problem
The most scathing criticism came when Theo examined the default .agents.md files that Vite Plus generates for AI coding assistants. These files are meant to give AI tools context about the project, but Vite Plus's implementation missed the mark.
"This is where I'm going to start having hot takes," Theo warned before diving in. The generated file included extensive documentation about Vite Plus commands, setup instructions, and implementation details—information irrelevant to an AI working within an already-initialized project.
"There's no reason that the agent needs to know the create command in a project that I've already created," he argued. "If I saw somebody try to commit this agent MD in one of my projects, I would probably yell at them."
He deleted both default agent files and recommended others do the same. Void Zero team members watching his stream confirmed these files are still being refined, but the larger point stands: when you're building tooling for AI-assisted development, the quality of that integration matters as much as the tool's core functionality.
What This Reveals
Theo's exploration illustrates a fundamental tension in developer tooling. Vite Plus wants to be comprehensive—to unify disparate tools into one coherent system. That's valuable. The web development ecosystem genuinely suffers from tooling sprawl, version conflicts, and configuration hell.
But comprehensive systems require opinions. They make choices about defaults, precedence, and workflow. Those opinions inevitably clash with how some developers—particularly experienced ones who've built custom workflows—expect things to work.
The question isn't whether Vite Plus is good or bad. It's whether its opinions align with how its target users actually work. An alpha release is precisely the time to surface these conflicts. Theo's willingness to test publicly and provide direct feedback serves both the project and potential users.
There's also a keyboard ergonomics complaint I can't entirely dismiss, even if it sounds absurd. Theo noted that typing vp requires two hands on a QWERTY keyboard, unlike npm, pnpm, or even bun, which can be typed one-handed. Trivial? Perhaps. But developers type these commands hundreds of times daily. Small frictions accumulate.
The Alpha Reality
None of these issues are fatal for an alpha release. That's rather the point of alpha—to find the sharp edges before they're set in stone. Void Zero has explicitly invited this kind of feedback.
What matters more is how the team responds. Will they reconsider command precedence? Will they streamline the AI integration files? Will they prioritize Bun support for their core audience? The answers will determine whether Vite Plus becomes the unified toolchain the web development world adopts or another promising project that couldn't quite bridge the gap between vision and practice.
For now, Theo's verdict is cautiously optimistic: "I see where they're going here. This is good stuff." But he's also clear about what needs fixing. That's probably the most honest assessment an alpha deserves.
Bob Reynolds is Senior Technology Correspondent for Buzzrag.
Watch the Original Video
I did not expect this...
Theo - t3․gg
30m 5sAbout This Source
Theo - t3․gg
Theo - t3.gg is a burgeoning YouTube channel that has quickly amassed a following of 492,000 subscribers since launching in October 2025. Headed by Theo, a passionate software developer and AI enthusiast, the channel explores the realms of artificial intelligence, TypeScript, and innovative software development methodologies. Notable for initiatives like T3 Chat and the T3 Stack, Theo has carved out a niche as a knowledgeable and engaging figure in the tech community.
Read full source profileMore Like This
JavaScript's Bloat Problem Is Worse Than You Think
Why your web app downloads millions of lines of unnecessary JavaScript—and who's responsible for the mess we're in.
How Node.js Cut Memory Usage in Half With One Change
A year-long collaboration between Cloudflare and the V8 team enabled pointer compression in Node.js, halving memory usage with minimal performance cost.
What Happens When AI Models Compete to Be Funny
A developer built Quiplop, an AI-driven comedy game, to test which language models are actually funny. The results reveal unexpected truths about AI.
Four Shadcn Component Libraries You Haven't Seen Yet
From gooey animations to sound effects to sci-fi interfaces, these open-source React libraries built on Shadcn show where UI development is heading.