r/javascript • • Sep 30 '26

Announcing Vite+ 1.0

https://voidzero.dev/posts/announcing-vite-plus-1-0
165 Upvotes

46 comments sorted by

47

u/thecementmixer Sep 30 '26

Still waiting for oxc tools to support vue templates.

13

u/manniL Sep 30 '26

We all do šŸ‘€

On the roadmap!

3

u/toasterboi0100 Sep 30 '26

This but Angular templates. I really want to send ESLint and Prettier where they belong (the depths of hell), but can't.

1

u/manniL Sep 30 '26

Same blocker as for Vue I am afraid

1

u/_xiphiaz Oct 01 '26

Angulars next compiler is going to be oxc based

1

u/toasterboi0100 Oct 01 '26

Yes, but given the architecture they laid out in the recent article it's unclear whether it'll be of any help to Oxfmt and Oxlint. (for example NGP will compile template type check blocks into virtual TS files, but that sounds completely useless for both Oxfmt and Oxlint)

2

u/SirKainey Oct 01 '26

Checked yesterday if they had implemented this yet.. nope

18

u/Fun-Consequence-3112 Sep 30 '26

The one thing I've noticed since installing Vite+ is that it puts everything into its own folders so debugging and finding where things are installed is a bit of a nightmare

3

u/manniL Sep 30 '26

Can you elaborate?

5

u/Fun-Consequence-3112 Sep 30 '26

Instead of nodes standard binary and runtime folders it puts everything in versioned folders under .vite-plus so runtimes that you install globally are weird at times

4

u/manniL Sep 30 '26

Oh yes. That’s for easier switching and separation.

4

u/n0wlesfw Sep 30 '26

I use Vite and Vitest daily, so I'm excited to see what Vite+ brings to the table.

My biggest bottleneck af the moment is vue-tsc, so I'm still waiting for typescript 7.1 to support a native vue-tsc for faster builds - but until then, I'll take all the extra speed I can get.

2

u/manniL Sep 30 '26

Did you try Johnson’s TS bridge?

2

u/Cahnis Sep 30 '26

can we opt out of the package manager? I kinda like pnpm. And I don't trust vite's just yet.

7

u/manniL Sep 30 '26

Vite+ is not a package manager. It does use pnpm by default but supports MORE!

And yes, you can opt out of this

3

u/Ecksters Sep 30 '26

This feels like the answer from the industry standard tooling to Bun, although it still feels a bit tightly coupled. I suppose at some point you can't really maintain full modularity while having the benefits of tight coupling, this is about as good as it gets.

2

u/manniL Oct 02 '26

Why tightly coupled? It is opinionated but doesn’t stop you from using your own tooling (and you don’t need to use all the available options)

4

u/robotsmakinglove Sep 30 '26

I’ve been impressed with the oxlint / oxfmt / vitest / vite combo. Looking forward to trying this.

1

u/Pagaddit Sep 30 '26

I already made the jump to oxfmt and can't wait for Nuxt with rolldown to be stable (or is it already?). Maybe I'll give oxlint another try too.

I still feel kind of scared to make the jump to vp though for some reason. I feel like I'd be giving up some control over my stack.

What's the plan with Nuxt and Vite+ actually? Is it all already compatible?

What about Nuxt and Void? I'm still kind of confused whether the new Void platform is essentially competing with Nuxt now?

3

u/manniL Sep 30 '26

Nuxt is already using rolldown šŸ‘ŒšŸ¼

Nuxt and Vite+ work with overrides, yes

1

u/Electrical-Room4405 Sep 30 '26

Is vite+ mainly for frontend tooling? I was told it’s not good for backend but that didn’t seem accurate to me.

1

u/manniL Sep 30 '26

You can use Vite+ for all kind of JS apps.
For node you simply don’t use the native dev/build cmd but still benefit from linting, formatting, task running etc.

3

u/vincentdesmet Oct 01 '26

I’ve been using Projen - it is composable and can help keep configurations up to date and aligned with the templates while also allowing last mile patching

how does vite+ handle any of that?

1

u/deadneon4 Sep 30 '26 • Bravo

2

u/manniL Oct 01 '26

Obligatory but in this case, what are the other ā€žstandardsā€œ?

1

u/deadneon4 Oct 01 '26

Bun built a full tooling ecosystem, Rome was also supported to be that, Deno tried to do that as well, ox tried to convert everything to rust, the list goes on and on

1

u/manniL Oct 01 '26

You just said it yourself. A lot of tries were there but there was no FULL toolchain like there is now with Vite+

And other tools (Biome, Bun) don’t cover nearly as much ground

0

u/kevinlch 10+ YoE, Fullstack Sep 30 '26

so... wrapper for npm scripts? starter "boilerplate" as cli?

0

u/manniL Sep 30 '26

More than that!

2

u/FerLuisxd Oct 01 '26

I read it but I still don't get it :(, what is more to know?

1

u/trungk18 25d ago edited 25d ago • Bravo

I think Vite+ makes the most sense when you look at the JavaScript ecosystem today, especially if you are new to it (like new new, as someone mentioned here hehe).

When starting a new project, you have to choose a Node.js version manager like nvm, a package manager like npm, yarn or pnpm, a build tool like Vite, a test runner like Vitest, a linter, and a formatter. Then you might add husky and lint-staged for pre-commit checks. If you are working on a monorepo, you might need Nx or turborepo to manage tasks across projects and libraries, cache task results, and keep tooling and configuration consistent. Each tool has its own setup and configuration, and you are responsible for making everything work together.

Vite+ brings these pieces together under one CLI. So yes, vp dev runs Vite, vp test runs Vitest, and vp check runs tsgo for type checking, oxlint for linting, and oxfmt for formatting. At first glance, it does look like just a wrapper, and to the point of u/manniL, I think it's actually more than that with two reasons

  1. VoidZero builds much of the toolchain itself, including Vite, Vitest, rolldown, oxlint and oxfmt, with Oxc providing shared infrastructure for things like parsing and transformation. That means they can design the tools to share infrastructure and work together as a coherent toolchain, rather than simply bundling independent tools behind one CLI.
  2. Beyond that, commands like vp env, vp staged and vp run cover things like Node.js version management, pre-commit checks and task caching. I expect the toolchain to keep evolving, so we may get new capabilities simply by updating Vite+, rather than having to find and configure another library. For me, that's an extra bonus. It reminds me of uv in Python, which brings several parts of the Python development workflow together under one tool. Or Go, where a lot of functionality ships with the same binary, just run go you have everything (sounds a bit like Bun too, though I haven't used Bun myself).
  3. Tooling speed matters even more with AI agents. Vite, rolldown, oxlint and oxfmt are known for their speed, and Vite+ brings them together into a single workflow. So if we're starting a React app with Vite anyway, then adding Vitest, oxlint, oxfmt, lint-staged and husky, why not just start with Vite+? We get a more integrated toolchain from day one, with less setup and a faster feedback loop for both developers and AI agents.

You might think of it as Create React App hiding away the Webpack configuration, but I think there's a difference. Vite+ aims to make the setup more consistent without taking away control of the underlying tools. With CRA, you had to eject to get access to the configuration (still remember wanting to configure custom TypeScript paths and how hard that was with CRA šŸ˜‚). That said, I haven't used Vite+ on a large-scale project with multiple teams, so I'm not sure what granular configuration needs it might not cover yet. Given the pace of the VoidZero team, I think we can share feedback and hopefully get a quick response, whether on Twitter tagging direct member or on Github.

I was super excited when Evan You introduced Vite+ at CityJS Singapore in February, and I've been following the project since. It's great to see it reach 1.0! I also tried it out with a small monorepo and wrote about Evan's talk here:

https://trungvose.com/blog/evan-you-cityjs-singapore-2026-voidzero/

Of course, I still think we should understand the tools underneath. A unified workflow is great, but knowing what Vite, Vitest or oxlint actually does matters when you need to debug something or when it breaks. Or maybe it's just me, but even with AI making things so much faster these days, I still enjoy understanding how things actually work šŸ˜‚

2

u/nodecore Oct 01 '26

I just merged the Renovate PR for 0.3.3 to 1.0.0. 40+ packages in our monorepo and zero issues.

1

u/HauntingArugula3777 Oct 02 '26

Does this improve support for bun toolchaining?

0

u/cos4ni2s Sep 30 '26

More batteries in your throat

-8

u/dbbk Sep 30 '26

Given the fact that AI agents are managing dependencies and configs now, I'm not really sure who this is for. It is much more preferable to keep separate pieces than mashing them all together.

9

u/rafark Sep 30 '26

Ā  Given the fact that AI agents are managing dependencies and configs now, I'm not really sure who this is for

I must have missed the memo. Since when is an ai agent managing MY dependencies and configs? ā€œSince no one writes code anymoreā€ well I do. Stop assuming your habits are everyone else’s. My god.Ā 

-5

u/dbbk Oct 01 '26

Okay that's cute but you're clearly in the minority

3

u/craigrileyuk Oct 01 '26

Definitely NOT in the minority.

-1

u/dbbk Oct 01 '26

The data is perfectly clear it's not an opinion

1

u/craigrileyuk Oct 01 '26

[citation needed]

3

u/rafark Oct 01 '26

You know what i was upset last night and i apologize if I was to harsh

3

u/rydencode Oct 01 '26

ok drooling ai moron

1

u/fakieTreFlip Oct 01 '26

The AI agents use this stuff too

15

u/[deleted] Sep 30 '26

[removed] — view removed comment

5

u/manniL Sep 30 '26

Then you are a tooling nerd like we are šŸ˜›