Turbopack: Building faster by building less

Posted by feross 4 days ago

Comments

Comment by pjmlp 3 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.

Comment by brylie 3 days ago

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

https://vite.dev/

Comment by rk06 3 days ago

turbopack is tightly coupled with next.js

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

Comment by icyJoseph 3 days ago

https://github.com/utooland/utoo/issues/1872 utoo uses Turbopack though

Comment by rk06 3 days 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.

Comment by o_m 3 days ago

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

Comment by chrisldgk 3 days ago

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

Comment by pjmlp 3 days ago

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

Comment by almaight 3 days ago

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

Comment by chrisldgk 3 days 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.

Comment by pjjpo 2 days 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.