- Yeah, it makes you wonder how much computing power the industry has wasted over the years on tools that nobody questioned because "that's just how long builds take." We planned our work around it, joked about creating breaks, and built entire caching layers to work around it.
Kudos to the Vite maintainers!
by homebrewer
3 subcomments
- Very pleased to see such performance improvements in the era of Electron shit and general contempt for users' computers. One of the projects I'm working on has been going for many years (since before React hooks were introduced), and I remember building it back in the day with tooling that was considered standard at the time (vanilla react-scripts, assembled around Webpack). It look maybe two minutes on a decent developer desktop, and old slow CI servers were even worse. Now Vite 8 builds it in about a second on comparable hardware. Another demonstration of how much resources we're collectively wasting.
- I contributed this change in Vite 8:
> Wasm SSR support: .wasm?init imports now work in SSR environments, expanding Vite's WebAssembly feature to server-side rendering.
While the process was relatively slow, I really appreciate the extra effort that the team have put on even this minor feature add. They not only guided me towards more compatible and idiomatic approach, but also added docs and helped keeping the code up to date before merging.
- Vite 8 is pretty incredible. We saw around an 8x improvement (4m -> 30s) in our prod build, and it was nearly a drop-in replacement. Congrats (and thank you!) to the Vite team!
- Thanks to the Vite team for building a faster, modern bundling solution on a fully open source stack that isn't tied to a specific framework...cough cough, Turbopack
by soulchild77
5 subcomments
- Awesome! Too bad Next.js will never profit from these incredible community efforts, because Vercel suffers from NIH.
- Vite+, Void Cloud, Void Framework... an epic battle between Vercel and Void is coming.
The PRC (aka server functions) demo [0] is particularly interesting — end-to-end type safety (from DB to UI) is a major milestone for JavaScript. We've been doing a lot of RPC design work in that space with Telefunc (tRPC alternative) [1] — it's a really hard topic, and we're looking forward to collaborating with the Void team. (Also looking forward to contributing as the creators of Vike [2].)
[0]: https://www.youtube.com/watch?v=BX0Xv73kXNk (around the end of the first talk)
[1]: https://telefunc.com (see the last PR)
[2]: https://vike.dev
- I've been using rolldown-vite for the past 3-4 months with absolutely no issues on a very large monorepo with SvelteKit, multiple TS services and custom packages.
Just upgraded to 8 with some version bumping. Dev server time reduced to 1.5s from 8s and build reduced to 35s from 2m30. Really really impressed.
by vite_throwaway
3 subcomments
- I have a small React project using vite 7 and have the following in my config so that vite interprets ".js" files as JSX:
// See https://github.com/vitejs/vite/discussions/14652
esbuild: {
loader: "jsx",
include: /.*\.jsx?$/,
exclude: [],
},
optimizeDeps: {
esbuildOptions: {
loader: {
".js": "jsx",
},
},
},
Note the comment at the top. I had no idea how to come up with this config by checking the documentation pages of vite and its various related tools. Luckily I found the GitHub issue and someone else had come up with the right incantation.Now this new vite uses new tools, and their documentation is still lacking. I spent half an hour trying to figure out how vite (and related tools that I had to navigate and try to piece a coherent view of: esbuild, oxc, rolldown, etc.) might be convinced, but gave up and stayed with vite 7.
Someone could respond with a working solution and it would help, sure, but these tools sure as hell have documentation issues.
- > Built-in tsconfig paths support
A great QoL change. One less place to duplicate (and potentially mistake) a config.
by chrisweekly
0 subcomment
- Awesome news. Amid all the (real and perceived) js ecosystem churn, vite has been consistently excellent for dx and production. The unified rolldown bundler is only going to increase vite's appeal and widen the gap as the fastest, most pragmatic and flexible foundation for ts/js projects.
Huge fan, speaking from deep experience (webdev since 1998).
by shunia_huang
1 subcomments
- Ah, wondering how long it will take Angular to replace it's sh*t building tool chain to fully vite compatible, hope it could happen before I change may career path or retire.
by Aldipower
4 subcomments
- As I am interested in long time maintainability (should still work in 10 years) with my projects I am just using esbuild directly. I am not interested in adjusting my projects, just because things changed under the hood in "wrappers" like Vite and I suddenly have a lot of work.
by brandensilva
1 subcomments
- Man the perf changes for this version are awesome. Thanks Vite.
- Sweet, great job Vite team!
I wonder how much of the Rollup bundling magic has been ported to Rolldown.
One thing that always made this kind of switch to Rust has always been that Rollup has become so sophisticated that's hard to replace with something new.
- Yesterday I stopped hating AI because it converted an old webpack project with impenetrable plugin settings to a single simple Vite config.
I still don't understand how people used to think scripts like this are the proper way to bundle an app.
https://github.com/facebook/create-react-app/blob/main/packa...
vite is great, is all I am saying
- Awesome! been using Vite since its early days.
really excited to see how it's improving the JavaScript and TypeScript tooling landscape and how it continues to evolve
by throwaway290
2 subcomments
- Outsider question: why use Rollup when Esbuild exist? Is esbuild not enough for production builds?
by slopinthebag
1 subcomments
- > Currently, the Oxc transformer does not support lowering native decorators as we are waiting for the specification to progress
Does Oxc also support TS runtime features like constructor parameter properties and enums? I seem to recall in the beta that they had enabled --erasableSyntaxOnly, presumably because Rolldown / Oxc didn't support doing a full transform.
by verma_yatharth
0 subcomment
- I tried it and I saw more than 6x improvement in speed.
It's on the top. Awesome tool 1
- Migrating straight away! Thank you!
- Congratulations!
by hackernewsman71
0 subcomment
- holy shit - Vite 8 - rhymes in french! Did they mention that somewhere?
- [flagged]
by raphaelmolly8
0 subcomment
- [dead]
- [dead]
by JulianPembroke
0 subcomment
- [flagged]
- Another rewrite in Rust.
What about finally stop using node.js for server side development?
Hacker News