5 ms·

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

• o_m 9mo ago
  Yes, TurboPack is for legacy projects that can't update from Webpack, but still want some bundle speed improvements.
  • chrisldgk 9mo ago
    Which is mainly NextJS (old and new), since under the hood that still seems to rely on Webpack.
  • pjmlp 9mo ago
    Not really, because they only ported into Rust the most used plugins with "yes but" constraints.
• rk06 9mo ago
  turbopack is tightly coupled with next.js rest of the JS community can't use turbopack, so they went with vite
  • icyJoseph 9mo ago
    [dead]
    • rk06 9mo ago
      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.
  • gempir 8mo 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 8mo ago
    Thanks for the clarification.
• deleted 8mo ago
  [deleted]