The Unified toolchain is an extremely ambitious project. when Rome announced their plan for unified toolchain, I expected it to fail as the next HN reader. and turned out to be right.
Bun is also attempting it. Thye have made tremendous progress but they are also competing against node, and thus I don't expect to for bun to go mainstream.
However, despite the difficulties, I strongly believe that Vite+ can achieve it.
I strongly recommend all readers here to watch Vite documentary[0] that got released less than a day ago for vite's history and bacground of Vite+
> Built for growing teams tired of configuring, patching, and replacing their JavaScript tooling stack.
Ah, great, another Javascript tooling stack! Let's jump on board! I'll get straight to configuring, replacing and patching as soon as possible. Or maybe let's just don't. I'm tired, Boss.
Vite works fairly well. Most config for other tools can (should?) be left at the defaults. Jest is falling apart but Vitest works very well. We've come a long way. Now let's freeze the web for some years!
Ehhhhh... what does this mean for the open source versions of all these libs? You could interpret some of the graphs as vite oss isn't getting rolldown. That would be disappointing but still okay.
I don't get it. If I'm looking for a new webdev stack, I would obviously want something free, open source.
A big "Request early access" followed by a contact form at the top of the landing page is an instant redflag of vendor locking, who would ever want that?
I'm very happy with Vite, this toolchain on top of it looks useful too, I would have preferred all that to just be part of vite (similar to bun) but I guess there are good reasons to keep the scope of core vite smaller?
Don't get me wrong but at this point you might as well just use Java instead of javascript to build web pages.
Vite is basically replicating what one would expect as normal behaviour from the JDK + IDE has been doing since years. Javascript was meant to be readable for an open web, nowadays it is compiled into a puddle of text.
It is OK to reinvent the wheel, it just doesn't look much better than the old one.
Interesting, I am a heavy user of vite today and the featureset is interesting but I don't really understand how it will differ from "normal" vite and why I would pay for it.
because it is a landing page. why would landing page not be prioritising beauty over size. honestly my standards have taken a lot of hit these days w.r.t. page size, so i don't think it is worse than average
I am wondering what vite+ will have that will really make it worth it compared to the "rstack" (i.e. rspack, rsbuild, rstest, rslint, etc.) rsbuild is already excellent and things like remote cache are on their roadmap?
The first and most important distinction is obviously which ecosystem you are more familiar / invested in (webpack vs. vite). It does make sense for projects deeply coupled to webpack to consider rspack first.
Putting that aside:
- Vite+ is a commercial offering with a company that can provide paid support. Rstack is a big corp by-product where their primary customers are internal teams.
- The Vite ecosystem provides way more options in choice of meta frameworks (Nuxt, Astro, React Router, Tanstack Start, SvelteKit, SolidStart...), and 3rd party tooling integrations
- While both written in Rust, our tools in general perform significantly better than rstack. With the upcoming full bundle mode, Vite 8 will be at least 2x faster than rsbuild across all categories (dev server start up, HMR, production build)
- Vitest and Oxlint are mature and widely used in production. rstest and rslint are both quite new and not even feature complete.
I recently had to setup another complex monorepo with eslint/vitest/vite/tsup/turborepo and it was such a pain. All the time either eslint breaks for some file, or some build breaks because of some obscure thing in tsconfig, turborepo behaves in a weird way, adding new packages is a pain, etc.
Hopefully Evan can pull this off and we have simpler initial setup.
I like Vite a lot, but (some feedback from the team) you need to give me more marketing up front to convince me why I would want more javascript. I already feel like I have too much. The comments here would echo the same.
Not shocking, a lot of time goes into making Vite and they need to make money.
One approach is to setup consulting services. Looks like Void Zero's approach is to start building value-add tools and features on top of Vite that are no longer free.
The decision that users must make now is whether it's worth the risk investing in Vite, assuming that more and more functionality will move to the paid tier.
I belong to the "small business" group and as such I would be entitled to "free" plan. But, I would actually prefer to pay and have the assurance that the team will be here to maintain it.
29 comments
[ 5.9 ms ] story [ 87.0 ms ] threadBun is also attempting it. Thye have made tremendous progress but they are also competing against node, and thus I don't expect to for bun to go mainstream.
However, despite the difficulties, I strongly believe that Vite+ can achieve it.
I strongly recommend all readers here to watch Vite documentary[0] that got released less than a day ago for vite's history and bacground of Vite+
[0] https://www.youtube.com/watch?v=bmWQqAKLgT4
As far as Astral goes, so far they've distributed all the tooling separately but it seems they might be going towards consolidation as well.
Ah, great, another Javascript tooling stack! Let's jump on board! I'll get straight to configuring, replacing and patching as soon as possible. Or maybe let's just don't. I'm tired, Boss.
A big "Request early access" followed by a contact form at the top of the landing page is an instant redflag of vendor locking, who would ever want that?
Vite is basically replicating what one would expect as normal behaviour from the JDK + IDE has been doing since years. Javascript was meant to be readable for an open web, nowadays it is compiled into a puddle of text.
It is OK to reinvent the wheel, it just doesn't look much better than the old one.
92 requests 22.6 MB transferred 25.2 MB resources Finish: 9.54 s DOMContentLoaded: 290 ms Load: 9.50 s
at least the page is a work of art
The first and most important distinction is obviously which ecosystem you are more familiar / invested in (webpack vs. vite). It does make sense for projects deeply coupled to webpack to consider rspack first.
Putting that aside:
- Vite+ is a commercial offering with a company that can provide paid support. Rstack is a big corp by-product where their primary customers are internal teams.
- The Vite ecosystem provides way more options in choice of meta frameworks (Nuxt, Astro, React Router, Tanstack Start, SvelteKit, SolidStart...), and 3rd party tooling integrations
- While both written in Rust, our tools in general perform significantly better than rstack. With the upcoming full bundle mode, Vite 8 will be at least 2x faster than rsbuild across all categories (dev server start up, HMR, production build)
- Vitest and Oxlint are mature and widely used in production. rstest and rslint are both quite new and not even feature complete.
Hopefully Evan can pull this off and we have simpler initial setup.
Vite: The Documentary https://www.youtube.com/watch?v=bmWQqAKLgT4
1. This is a Vite rugpull, right?
2. What the hell do I migrate to to avoid the rugpull, now?
Lots of stuff builds on top of Vite, and this is an incredibly bad move from the Vite people.
I would love more information about this feature! Bad line-wrapping is the reason I loathe Prettier.
One approach is to setup consulting services. Looks like Void Zero's approach is to start building value-add tools and features on top of Vite that are no longer free.
The decision that users must make now is whether it's worth the risk investing in Vite, assuming that more and more functionality will move to the paid tier.
Please list the prices.