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+
The sestertius isn't what it used to be.
It was also unfortunately timed. When they started they were competing against webpack, but right around the start of the project compilers written in more performant languages like ESBuld and SWC start to take off and out compete Rome before it even got off the ground.
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?
Eventually you'll need to migrate away or cough up serious money. So yeah, not sure who'd go for this.
Mind you we use NX at the moment and that was quick and easy enough to set up with no major issues for years now, so I wonder what the USP of this tool is. We also use Vite in some projects in combination with NX so maybe this is mainly aimed at that.
I'm concerned that it erodes trust into vite and makes all the other open source maintainers contributing to /the commons/ asking some questions.
There is nothing really special about vite too. It's important, sure, but there is a lot of important open source projects that also need funding. Can all of them pull the same trick?
As for why? some people have very large codebase and prefers their developers to have better UX and are willing to pay for it. lower CI/CD server costs also directly translate to cost savings if you are Replit or stackblitz,
You may not like it, and that is ok. as individual developers are already benefitting from vite. and will get rolldown soon.
Are you affiliated with this project? Based on your comment history, you seem to be
92 requests 22.6 MB transferred 25.2 MB resources Finish: 9.54 s DOMContentLoaded: 290 ms Load: 9.50 s
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.
Before Vite+, we maintain Vite, Rolldown, Oxc, all of which are open source and widely used. These remain open source - nothing changes about existing projects.
Vite+ is an entirely new product built on top of our own open source, with additional features that are entirely new. You don't need to use Vite+. You can keep using all the open source that we already provide.
The revenue generated from Vite+ flows back into the development of both its proprietary features the underlying OSS. So if you are a user of our OSS, you'd benefit from Vite+ even if you don't use it, because it allows us to keep improving the OSS you are using.
2. Nothing because Vite is OSS and this is something extra on top for managing everything else people usually use on a project.
Did you watch the keynote from the conference today? The conference attended by all the people who you see as great contributors to the Vite project?
They want this. This is good for the ecosystem to maintain funding as a whole.
I did not watch any keynote and frankly place exactly 0% faith in the words of the people behind this move. The rugpulls we have seen so far have all been shady business moves mostly by dishonest people, so that is my expectation.
It's like every acquisition ever, they say nice words at the time it happens, reality unfolds later: https://ourincrediblejourney.tumblr.com/
I see nothing here but yet another Open Core project that will be utterly irrelevant in 1-3 years.
Voidzero Inc owns the Vite trademark:
https://tsdr.uspto.gov/#caseNumber=98845059&caseSearchType=U...
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.
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.
All functionality as part of OSS projects will stay there. OSS projects such as Vite, Vitest, Rolldown and Oxc will stay open source.
Eventually, the (financial) success of Vite+ is directly tied to the health, stability, and adoption of the free, open-source Vite ecosystem, so the incentive is rather low.
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.
Vite: The Documentary https://www.youtube.com/watch?v=bmWQqAKLgT4
Please list the prices.
If anything, FE tooling starts looking like it moves to more sane place. Also Anthony Fu is cool
previously (i.e. before current viteconf), Evan had said that existing OSS (vite and below) will remain OSS. only newer tooling will be monetised
This is not good news.
Vite already has rolldown support in the current version, it's just in alpha/test stage.
https://vite.dev/guide/rolldown.html#how-to-try-rolldown
Nothing is keeping them to this plan other though, I hope they do follow through. That would make the graph on the page misleading in the other direction though as the speed feature would be included in the non plus version.
I want to also say I'm a happy vite user (and the other projects that team makes).
I would love more information about this feature! Bad line-wrapping is the reason I loathe Prettier.
Hopefully Evan can pull this off and we have simpler initial setup.
Vite+ is a tool similar to Rust Cargo or Go's toolchain that handles building (via Vite), testing, linting and formatting.
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.
The current dominant toolchain has been very stable for years now, and is much better than the mess of Webpack/Rollup/Brunch/Grunt/Gulp/Bower/Browserify/Parcel/Snowpack/Turbopack/Babel/etc/etc.
The only problem is that NOW there are too many separate different tools that aren't bundlers, so in addition to Vite one also has to configure Prettier, Eslint, Vitest, Typescript, Husky, Lint-Staged, Playwright, DotEnv, what else?
A unified toolchain might not replace each and every tool above, but it will simplify a lot of this process.
It will also simplify migrating between tools that it doesn't intend to replace, like migrating between Typescript and Typescript-Go. Etc.
This is already the reality in Go, Rust and other languages.
For NextJS, do you remember the runtime used for middlewares? What was this swc thing again?
It never ends. Every year new things are added and they never really replace anything, it's just one more thing to learn and maintain.
If every technology causes exactly 1 issue per week then you quickly spend 50% of your time fixing bugs that have absolutely zero to do with what your company is actually doing.
---- EDIT
And it doesn't even stop at issues. Every one of those technologies regularly goes through breaking changes. In the process, plugins are deprecated, new ones have completely different APIs. You want to upgrade one thing for a security fix, then you're forced to upgrade 10 other things and it spirals out of control and you've spent entire work days just sifting through change logs to change `excludeFile` to `excludedFile` to `includeGlob` to `fileFilter` to `streamBouncer` to I don't know what.
The only two tools I like in the JS world is `yarn` and `prettier`. They're focused and do what they do well. But you add eslint and any of the others and their configuration is a full fledged turing machine. Even autotools feels nice in comparison to that mayhem.
What? That mess is still ongoing. Next.js for example (probably the most popular "out of the box" solution) technically uses SWC, but not quite, because it doesn't support `styled-components` so you need to use Babel for that. But wait, you might also need to use tailwind, and for that you'll need `postcss` which might also work with Babel with `babel-plugin-import-postcss` but not necessarily, could also just use it as a Next plugin, but that doesn't always[1] seem to work.
I don't think this mess will ever end unless we throw React/Vue, and all "reactive" frameworks in the dustbin and we'll get enough folks on board to re-invent the web starting from scratch. But no one really wants to do that (yet?), so even things like Bun or Deno will try to be as compatible as possible making continuous concessions that will lead to the ongoing spaghettification of toolchains.
This less a problem when your project is on the web though, because vite (and I think under the hood esbuild) transforms the imports gracefully.
You do know that Vite uses a lot of these behind the scenes right? Vite in general has much better defaults so that you don't have to configure them most of the time, but anything a bit out of the box will still require messing with the configs extensively.
Not like OPs Vite+ changes anything regarding that.
Especially eslint with their decision to change configuration format in a way that breaks all and every plugin, tutorial, project in existence as a giant "fuck you" to the whole ecosystem and all web developers of the world.
Jesus, it's bad enough I can't leave a js project for 6 months without it starting to rot. Now my cynicism has to be updated too?
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.
Works great.
But the requirements of "modern" software are always changing. Sure, the static table might be enough, but then some business person says, "It sure would be nice if I could check a little box in the table row or assign this user here..." and now you're adding little JS hacks. Again, not impossible, but at a certain scale, the ability to have infinite access to client driven reactivity becomes a real business empowerment.
Given the interest in the JS working group to add reactive Signals to the core language, I suspect this will only become _more_ prevalent in the future. Maybe it will need less input from frameworks to do the same work and we can move back towards using built-in browser APIs, but the programming model itself works really well (so much so that SwiftUI uses a very similar reactive UI programming model).
Again, I don't disagree with your point, just at a certain scale, it becomes a huge hassle to maintain. If people are going to use these tools and frameworks anyway, it helps the entire web to make them more efficient.
It pains me that so many SaaS go for Next.js based SDKs, but at least it is the closest to Spring/Quarkus/ASP.NET in spirit.
It is so different when compared to Java/.NET where organizing large code blocks and making sure the pieces work well together is so easy. Very frustrating as there is so much that can be done on a browser but hampered by a development environment not much different from only using a text editor.
