from Hacker News

Vite+ – Unified toolchain for the web

by sangeeth96 on 10/10/25, 9:53 AM with 148 comments

  • by rk06 on 10/10/25, 10:24 AM

    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+

    [0] https://www.youtube.com/watch?v=bmWQqAKLgT4

  • by Galanwe on 10/10/25, 11:41 AM

    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?

  • by __jonas on 10/10/25, 11:48 AM

    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?

  • by shreddit on 10/10/25, 12:24 PM

    Why does you landing page download 25MB of pictures?!

    92 requests 22.6 MB transferred 25.2 MB resources Finish: 9.54 s DOMContentLoaded: 290 ms Load: 9.50 s

  • by yencabulator on 10/10/25, 5:11 PM

    Two questions:

    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.

  • by hv42 on 10/10/25, 12:28 PM

    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?

  • by watty on 10/13/25, 7:59 PM

    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.

  • by yakkomajuri on 10/10/25, 11:13 AM

    I guess this is similar to what Astral is doing on the Python side?

    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.

  • by vanni on 10/10/25, 4:41 PM

    Relevant:

    Vite: The Documentary https://www.youtube.com/watch?v=bmWQqAKLgT4

  • by selectnull on 10/15/25, 2:52 PM

    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.

    Please list the prices.

  • by staticelf on 10/10/25, 12:09 PM

    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.

  • by johnnypangs on 10/10/25, 11:23 AM

    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.

  • by jonathanhefner on 10/10/25, 9:38 PM

    > Vite Format: "More flexible line-wrapping"

    I would love more information about this feature! Bad line-wrapping is the reason I loathe Prettier.

  • by diiiimaaaa on 10/10/25, 12:58 PM

    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.

  • by epolanski on 10/10/25, 12:32 PM

    When do they expect to launch it?

  • by cadamsdotcom on 10/10/25, 7:17 PM

    Stick around maybe 10-20 years and then - maybe - you’ll be a contender.

  • by ttoinou on 10/10/25, 12:14 PM

    I have a hard time understanding what Vite does, so Vite+...

  • by bananapub on 10/10/25, 11:35 AM

    just one more layer of tooling bro, just one more layer

  • by petesergeant on 10/10/25, 11:58 AM

    Vite has been a joy to use. Very interested in an all-in-one solution from that team.

  • by avhception on 10/10/25, 11:23 AM

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

  • by ochronus on 10/10/25, 1:33 PM

  • by andai on 10/10/25, 11:45 AM

    It works with bun and deno too. That's really cool, I've never heard of a thing that works across runtimes like that.

  • by game_the0ry on 10/10/25, 1:19 PM

    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.

  • by nunobrito on 10/10/25, 12:00 PM

    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.