top | item 46702522

(no title)

brylie | 1 month ago

I may be out of the loop, but isn't the JS/TS community consolidating around Vite?

https://vite.dev/

discuss

order

rk06|1 month ago

turbopack is tightly coupled with next.js

rest of the JS community can't use turbopack, so they went with vite

gempir|1 month ago

Kind of weird way to put it. Turbopack was not a real product for years. It was forever stuck in weird beta/alpha stage and only recently went and became the default for NextJS.

Vite has been stable for years at least 5 years now and is built-upon because it's fast, stable, reliable and a bit less complicated than Webpack.

brylie|1 month ago

Thanks for the clarification.

icyJoseph|1 month ago

[deleted]

o_m|1 month ago

Yes, TurboPack is for legacy projects that can't update from Webpack, but still want some bundle speed improvements.

chrisldgk|1 month ago

Which is mainly NextJS (old and new), since under the hood that still seems to rely on Webpack.

pjmlp|1 month ago

Not really, because they only ported into Rust the most used plugins with "yes but" constraints.