| ▲ | brylie 5 days ago |
| I may be out of the loop, but isn't the JS/TS community consolidating around Vite? https://vite.dev/ |
|
| ▲ | 6 hours ago | parent | next [-] |
| [deleted] |
|
| ▲ | rk06 5 days ago | parent | prev | next [-] |
| turbopack is tightly coupled with next.js rest of the JS community can't use turbopack, so they went with vite |
| |
| ▲ | gempir 2 hours ago | parent | next [-] | | 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. | |
| ▲ | icyJoseph 5 days ago | parent | prev [-] | | [dead] | | |
| ▲ | rk06 5 days ago | parent [-] | | That project is working towards "mako next" project and is actually talking to vercel devs. So it may make sense to them. But that is not representative of broader ecosystem. |
|
|
|
| ▲ | o_m 5 days ago | parent | prev [-] |
| Yes, TurboPack is for legacy projects that can't update from Webpack, but still want some bundle speed improvements. |
| |
| ▲ | chrisldgk 5 days ago | parent | next [-] | | Which is mainly NextJS (old and new), since under the hood that still seems to rely on Webpack. | |
| ▲ | pjmlp 5 days ago | parent | prev [-] | | Not really, because they only ported into Rust the most used plugins with "yes but" constraints. |
|
