What is Turbopack?
Vložit
- čas přidán 29. 06. 2024
- Matt Pocock from Vercel talks you through Turbopack, the successor to Webpack. Turbopack is in Alpha right now, meaning it only works with Next in development mode. Learn more: vercel.fyi/tryturbo
00:00 What is Turbopack?
00:48 Try it out
01:44 Turbopack vs Vite
03:14 Turbo engine
04:38 The Future of Turbopack
05:36 Webpack's Successor - Věda a technologie
Really important! please work with storybook team, please do not abandon that team, storybook is an essential tool for us to do component driven development, really important for the community.
Waiting on Tailwind + postCSS support.
We are working on this! In the meantime, you can use Turbopack with Tailwind CSS as follows: turbo.build/pack/docs/features/css#tailwind-css
@@VercelHQ amazing updates !!!
This gets me so hyped! Keep up the good work!!!
Parcel 2.8 came out few weeks ago and is apparently even faster than Turbopack and not in alpha. It's nice seeing all these tools battle like this.
I like Parcel since it's so easy to get started with a bunch of different languages, but I don't use it much anymore since I kept running into issues with the hot reloading.
@@jacoblockwood4034 I haven't used Parcel, but I do know about it. Apparently some of the things inside Turbopack were inspired by Parcel.
It's maybe a shame Vercel created Turbopack and are wasting dev resources when they could have teamed up with Parcel potentially. I guess there was some reason not to do it.
Where did you get the info about Parcel being faster than Turbopack? I'm pretty interested, because it's hard for JS to compete against Rust in terms of performance 😅
@@DEVDerr Official Rust blog post for 2.8.0 release. They used the same benchmark Evan You (Vite creator) used to compare Vite to Turbopack after Vercel announced Turbopack.
Btw, as far as I know Parcel 2 is Rust based so that's why it can be so fast.
Parcel is an excellent tool but I use to have issues with the hot reloading, sometimes It can't find the index and is frustrating to run the server over and over again when I make changes
That is exactly what I needed !
Not sure how viable it'd be, but maybe it'd help if there were guides on moving from CRA or Webpack to Turbopack.
If so, from my experience, I'd say focus more on CRA, as someone who's had experience moving a large app from CRA to Vite and having to solve the issues of the node_module polyfills and whatnot. This is versus Vite which feels like it barely includes any more than what is needed.
We are currently working with turborepo in our big monorepo, and one of my colleague said: “it fast because it doesn’t check anything “ and it is true, caching algorithms works pretty badly. Hope turbopack will work better
I tried turbopack just yesterday on latest, didn't work for me it stalls out.
I had no clue that this guy worked at Vercel!
I'd love Turbopack to power Vite. I am a Svelte Kit dev myself and I would love Turbopack to bundle my apps.
Since rich is now working at vercel, and the roadmap directly has first class svelte support, sveltekit may just use turbopack directly
Very excited for this! Will there be WASM Turbopack distributions that we can run in the browser?
Whats the point of this
I've tried it with Turborepo and --turbo makes the app crashing in runtime with the error Error: Cannot find module 'next/dist/server/node-polyfill-fetch'
Once I remove --turbo, Turborepo project works fine
The fatal disadvantage of the monorepo is that debugging settings are not available on vscode.
Any updates for framer motion 🥺
Correct me if I'm wrong, but basically turbopack trades time complexity for space complexity right?
“Incremental computation engine” sounds a lot like old Makefiles, to me
My turbopack stuck at ready state for 1 hour 😂
4:00 it seems turbo is reinventing 50 year old make: make looks at file timestamps and knows what to rebuild… 😊
I'm just getting started and It's exciting af.
another bundler 😐 but betting on the rust
open source benchmark or bullshit!
turbo.build/pack/docs/benchmarks
Webpack always make it work more work, it is a wrong pack.
Vite is using esbuild, your "turbopack" can not be faster than esbuild