Recap: Next.js Conf 2024

Since last year's conference, we’ve:

• Released 5 new versions of Next.js

• Merged 4,000+ pull requests

• Welcomed 570 new community contributors

• Crossed over 7 million downloads per week, making it the world’s most popular frontend framework according to StackOverflow Developer Survey and State of JavaScript

We also released a new Next.js community GitHub organization, which to start contains ten different templates for deploying Next.js to your favorite providers. In the future, we hope to also include community adapters and other resources here.

As a thank you to our community, all Next.js Conf ticket proceeds have been donated back to open source projects that make Next.js possible.

Copy link to headingKeynote: Make it work, make it right, make it fast

This year’s keynote outlined how Next.js aligns with three simple principles:

• Make it work: More predictable data fetching and rendering with a refined App Router model

• Make it right: Turbopack for development is now stable—reduction in memory usage, faster initial compilation for large pages, improved error messages and trace stacks, and more to help you iterate with confidence

• Make it fast: Fewer, more powerful, and more flexible APIs for easier caching

Copy link to headingSimplifying complexity

Complexity can be a blocker. To address this, we’re changing how we present the framework through progressive disclosure of complexity. Meaning, if you’re building something simple, you won’t be overloaded with unnecessary details. And if you need advanced features, they’ll be available when you’re ready.

Based on your feedback, we've re-evaluated Next.js App Routers caching semantics. With Next.js 15, we're changing GET Route Handlers and the Client Router Cache from cached by default to uncached by default.

We're continuing to improve caching in Next.js. Learn more about what's next in our journey with caching. This is still experimental and not ready for production. If you try it out, we'd love your feedback.

Next.js remains a powerful tool for projects of all sizes, but we’re committed to making it feel effortless for every stage of development.

Copy link to headingTurbopack Dev is now stable

Turbopack is now stable for development. With the latest version of Turbopack, you can expect up to 90% faster code updates versus our previous version, thanks to incremental builds and optimized caching. That means fewer interruptions and faster iterations, so you can stay in your flow.

Learn more about Turbopack Dev reaching stability. With this milestone accomplished, we’re shifting our focus to Turbopack for builds. You can track our progress by visiting areweturboyet.com/build.

Copy link to headingBetter education for self-hosting

We released a new video tutorial showing how to configure Next.js features like improved image optimization, caching, ISR, streaming, middleware, server components, and more in a self-hosted setup.

Additionally, in Next.js 15, you can now configure the expireTime value in next.config.js. This was previously the experimental.swrDelta option and updating the default value to one year, ensuring most CDNs can fully apply the stale-while-revalidate semantics as intended. This is important for self-hosting applications when you may need more control over Cache-Control directives.

Copy link to heading​And so much more

Next.js 15 is officially stable and ready for production. Learn more about all the latest features and improvements in our blog post.

Copy link to headingThank you Next.js community

The community's dedication to open-source contributions, innovative ideas, and constant support is what drives Next.js forward. Every line of code contributed, every issue reported, every feature request, and feedback helps us improve and evolve—we can’t wait to see where the next year takes us.

Check out the recorded sessions here.