Turbopack, the successor to Webpack (vercel.com)

Article summary

Vercel has introduced Turbopack, a new high-performance bundler for React Server Components and TypeScript codebases, which is claimed to be 700x faster than Webpack on large applications. Turbopack is built on an incremental architecture and uses caching to skip large amounts of work. It is currently available in alpha and will be used for Next.js 13 development server. The goal is to eventually power Next.js production builds and provide an incremental migration path for Webpack users.

Main themes

• Turbopack performance
• Rust and compiled languages
• Webpack comparison
• Next.js integration
• Tooling and build processes
• Speed and performance tradeoffs

What commenters say

• Turbopack's speed improvements are significant and will likely lead to its adoption, but its alpha status means it still needs testing and development.
• The use of Rust and caching in Turbopack's architecture is a key factor in its performance gains.
• Some commenters are skeptical about the long-term benefits of Turbopack, citing potential complexities and limitations in its configuration and compatibility.
• Others see Turbopack as a positive development in the trend towards using compiled languages like Rust for tooling, which prioritizes speed and performance.
• There are concerns about the potential for Turbopack to become as complex and difficult to configure as Webpack, despite its initial promises of simplicity.
• The relationship between Turbopack and other tools like Rome and Vite is seen as potentially complementary, with opportunities for integration and cooperation.
• Some argue that the focus on speed and performance in tooling like Turbopack may come at the expense of maintainability and releasing high-quality software.
• The use of a JS layer for configuration while the core runs in Rust is seen as a viable approach, but may also introduce complexities and compatibility issues.