Turbopack: Building faster by building less

(nextjs.org)

15 points | by feross 2 days ago ago

11 comments

  • pjmlp 2 days ago

    Much less indeed, not all Webpack plugins capabilities are supported and now anyone that wants to make one has to learn Rust, which surely isn't the same as writing it in JavaScript.

    The splitting communities effect always gets left out of these announcements, or gets positioned as something good.

  • brylie 2 days ago

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

    https://vite.dev/

    • rk06 a day ago

      turbopack is tightly coupled with next.js

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

    • o_m 2 days ago

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

      • chrisldgk a day ago

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

      • pjmlp a day ago

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

  • almaight 2 days ago

    This thing can't be replaced by bun on Linux.

    • chrisldgk a day ago

      Is this a quip I’m not understanding or is there really something here that bun‘s bundled wouldn’t be able to do? Because I can’t find anything.

      • pjjpo 9 hours ago

        Not to say it is the quip but I have had buggy builds with bun that requires sticking to esbuild, I think it was bundling prettier with many plugins into a single JS file.

        I always do that sort of thing in Docker so never considered it could be a Linux-specific thing, maybe so.