Vite+ Beta • Hacker News Board

Re: Vite+ Beta

#51

Post by deadbabe » Thu, Jul 02, 2026, 1:39 PM UTC

It’s a great move for Cloudflare to have bought up voidzero.

Re: Vite+ Beta

#52

Post by CharlesW » Thu, Jul 02, 2026, 1:41 PM UTC

donaldstuck wrote: post #41

Doug McIlroy once said: "Make each program do one thing well".

Then he'd love this. Like Unix, Vite+ is a collection of programs that do one thing well.

Re: Vite+ Beta

#53

Post by ewy1 » Thu, Jul 02, 2026, 1:41 PM UTC

it worked for uv so i can imagine a competent team can do the same thing for javascript!

Re: Vite+ Beta

#54

Post by [deleted] » Thu, Jul 02, 2026, 1:45 PM UTC

khurs wrote: post #8

colesantiago wrote: post #7

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.

Says: "It is fully open source under the MIT license"

[deleted]

Re: Vite+ Beta

#55

Post by sailorganymede » Thu, Jul 02, 2026, 1:46 PM UTC

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.

Re: Vite+ Beta

#56

Post by csomar » Thu, Jul 02, 2026, 1:47 PM UTC

overflyer wrote: post #23

Layer on layer on layer on layer on layer.... Web development is just a meme by now

Is everyone project so simple that it can fit in these "vp check" / "vp dev" commands? Like even for my amateurish web app, I have a custom web server with a self-signed certificate with an "/etc/hosts" domain; and for checks I need to do custom checks for GraphQL and a couple of cloned NPM packages.

Re: Vite+ Beta

#57

Post by beaker52 » Thu, Jul 02, 2026, 1:49 PM UTC

sailorganymede wrote: post #55

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.

This is the latest emerging "boring but works" stack.

Re: Vite+ Beta

#58

Post by jstnh » Thu, Jul 02, 2026, 1:51 PM UTC

sailorganymede wrote: post #55

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.

the other tools are for testing, bundling, linting and formatting. Previously you would use different tools from very different open source projects for these things, with different configurations, update cycles etc. Now it's all covered by one simple toolchain. Vite+ is basically the "boring but works" stack, while also being more performant and with less configuration required.

Re: Vite+ Beta

#59

Post by KronisLV » Thu, Jul 02, 2026, 1:52 PM UTC

GCUMstlyHarmls wrote: post #50

KronisLV wrote: post #22

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).

> Sure beats opening some ancient project and seeing some mix of Vite, Vitest, Oxlint and Oxfmt and a bunch of other disjointed stuff (I migrated that one over to also use the newer stack).

I mean if I see those in N years, I'll be happier than with the older stack that came before them - the jank levels seem to generally be decreasing with every next attempt to get things right!

Re: Vite+ Beta

#60

Post by inbx0 » Thu, Jul 02, 2026, 1:54 PM UTC

curtisblaine wrote: post #3

ivanjermakov wrote: post #2

Can it be used for Node builds or browser-only same as Vite?

I'm always curious of the use case when someone proposes Node code bundling. What's the advantage? Obfuscation in SEA?

For me, the main benefit is deployment bundle/artifact size reduction. Mostly from dropping unneeded files from node_modules. Many packages include both esm and cjs builds, sources, docs, TS types, etc. stuff that you don’t need in prod. This matters for lambdas, for example, because deployed code size has limits there.