by sailorganymede
14 subcomments
- I am a big fan of Vite. But I have zero clue what those other tools are. I swear to God, I just put my head down to do some work and all the sudden, frontend tooling has evolved. I wonder if there is a push towards a "boring but works" stack.
- I love Vite, Vitest, Oxlint and Oxfmt and look in their direction for most of my new projects! I hope these folks manage to get a bunch of money and can fund the continued development for at least the next decade.
Sure beats opening some ancient project and seeing some mix of Gulp, Grunt, webpack and a bunch of other disjointed stuff (I migrated that one over to also use the newer stack).
by montroser
6 subcomments
- Vite had five major version in the four years 2022-2026. Version 3 => 4 => 5 => 6 => 7 => 8. Each one of those had breaking changes and required devs to go through a migration. It's too much. And for what? It's not as if it is dramatically better now than it was in version 3.
I can't say I would really look forward to bringing this level of needless churn and constant disruption to the rest of my development toolchain. Anyway, Vite+ is really just wrapping existing tools into an abstracted command-line interface? And so I have more layers of indirection to wade through in order to get the thing to do what I want? So far I am not optimistic about this prospect...
- Extremely happy user of Vite, Vitest, Rolldown, tsdown, Oxlint, and Oxfmt.
I do have lot of hardforked packages, and dont want to look back. Everything just works.
If you confused by the naming, start from Oxlint https://oxc.rs/docs/guide/usage/linter Rolldown https://rolldown.rs/
Did very little changes to tsconfig during past 6 months adoption
My day-to-day process - get the new package unless it some antd6, echart or some rendering engine or geo spatial lib, clean up with Claude, strict and unify type system and align it with my vite, tsconfig, oxlint tastes. The result - no need to follow libs bloat and supply chain attack issues. Easy to read, easy to fix.
- I think they should find a better name for this project. I find it very confusing since it's not really a better Vite.
At the time Void Zero was probably looking to monetize the Vite brand but now that they've been acquired by Cloudflare they don't need to do that anymore.
by ronbenton
3 subcomments
- Truly have so much trouble keeping up with the frontend (or JavaScript?) ecosystem. I so miss working in laravel. Wish more jobs paid well to use it.
- it worked for uv so i can imagine a competent team can do the same thing for javascript!
by ivanjermakov
4 subcomments
- Can it be used for Node builds or browser-only same as Vite?
by colesantiago
4 subcomments
- Is there a subscription with this?
I'm just wary about anything with a '+' and I assume there is a subscription attached to it.
Looking at this it doesn't look like it.
by dkdbejwi383
0 subcomment
- Toolchain Grand Vitesse
- Can I use Astro with this?
by donaldstuck
1 subcomments
- Doug McIlroy once said: "Make each program do one thing well".
by noodletheworld
1 subcomments
- I appreciate the effort to bring things together in this but…
> Vite+ will manage your global Node.js runtime and package manager.
What? Why?
You’re really going all-in if you adopt this; and… for what? A bit of cozy tooling around existing standard ways of doing things?
Ok, sure; I like tools, like vite.
…but even for an opinionated tool, this is extraordinarily opinionated. Like next.js
Im skeptical.
The pitch of bringing things together seems strong, but did we go too far here?
Reading reviews of people using this didn't really convince me.
It seems to be running on the coat tails of the vite name, rather than its own merit.
- That "+" is making me really nervous. Is this just a naming quirk, or the start of them trying to monetize Vite? If the latter, this is a dark day for frontend dev.
by overflyer
8 subcomments
- Layer on layer on layer on layer on layer.... Web development is just a meme by now
- It’s a great move for Cloudflare to have bought up voidzero.
- [flagged]
by incrudible
2 subcomments
- I have removed vite because dev build and reload is noticable slower than just esbuild and browser refresh. Vite does nothing for me that an LLM can not just trivially rebuild in a bespoke manner.
YMMV
- Vite pumps out major versions -- that is, breaking changes -- at an incredible rate.
I don't want to be a vite upgrade engineer.
I'll try to pass on this if I can.
Hacker News