Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Turbopack, the successor to Webpack

vercel.com

Post reply on HN
Print view View original

11–20 of 331 posts

Re: Turbopack, the successor to Webpack

#11

Post by brundolf »

hmillison wrote: post #5
samuelstros wrote: post #3

Vercel is on a streak. I am curious whether Turbopack elapses Vite like Vite elapsed Webpack over the past 12 months.

according to the article, Turbopack is 10-20x faster than Vite. I wonder how they were able to edge it out so significantly!

I would guess they're factoring this in:

> Turbopack is built on Turbo: an open-source, incremental memoization framework for Rust. Turbo can cache the result of any function in the program. When the program is run again, functions won't re-run unless their inputs have changed. This granular architecture enables your program to skip large amounts of work, at the level of the function.

Which would make that multiple an extremely rough estimate, highly-dependent on the situation. But it's still an exciting development

Re: Turbopack, the successor to Webpack

#13

Post by fabian2k »

hmillison wrote: post #5
samuelstros wrote: post #3

Vercel is on a streak. I am curious whether Turbopack elapses Vite like Vite elapsed Webpack over the past 12 months.

according to the article, Turbopack is 10-20x faster than Vite. I wonder how they were able to edge it out so significantly!

The answer seems to be caching (https://turbo.build/pack/docs/core-concepts), lots and lots of caching. Which enables it to reuse a lot of already computed stuff for incremental rebuilds.

Re: Turbopack, the successor to Webpack

#14

Post by jdelman »

Very excited for this if the configuration and behavior is 1:1 with Webpack. The primary reason I haven't moved to other "more efficient" build tools is having to learn how to do various optimizations and getting the artifacts I expect.

Re: Turbopack, the successor to Webpack

#16

Post by vidyesh »

samuelstros wrote: post #3

Vercel is on a streak. I am curious whether Turbopack elapses Vite like Vite elapsed Webpack over the past 12 months.

It is still in alpha, I am guessing a lot of backward compatibility might still be added to it before the stable release.

And the article exclusively testing it against just Next.js build could be an indicator as of how optimized it is for the meta framework probably?

Re: Turbopack, the successor to Webpack

#19

Post by TheRealPomax »

jdelman wrote: post #14

Very excited for this if the configuration and behavior is 1:1 with Webpack. The primary reason I haven't moved to other "more efficient" build tools is having to learn how to do various optimizations and getting the artifacts I expect.

God, I hope not. If there's one part of webpack that needs a complete overhaul it's (1) how you set up complex workflow configurations and (2) proper documentation for all aspects of that. And yes, that's one thing. Code without docs is not production-ready code, but code with bad docs isn't even PoC-ready code.
Post reply on HN