What's New in Next.js 15: A Developer's Guide

Key Takeaways

• Turbopack became the default bundler in development mode with 5x faster cold starts and 10x faster HMR.
• React Server Components matured with better error handling, improved streaming SSR, and partial prerendering.
• Next.js 15 shaped modern Next.js development and paved the way for Next.js 16's React Compiler integration.
• Server Actions stabilized the backend-for-frontend pattern, making the backend just a folder inside the frontend repository.
• Meta-framework configuration is production infrastructure, not boilerplate. Review middleware, server functions, and data access patterns with the same rigor as a dedicated backend service.

Next.js 15 brought significant improvements to the React framework, and with Next.js 16 now available, it's worth reviewing the features that shaped modern Next.js development.

Key Features in Next.js 15

Stable Turbopack

Turbopack became the default bundler in development mode, offering:

• 5x faster cold starts
• 10x faster HMR (Hot Module Replacement)
• Near-instant route changes

Improved Server Components

React Server Components became more mature with:

• Better error handling and error boundaries
• Improved streaming SSR
• Partial prerendering (experimental)

Enhanced Caching

Next.js 15 refined its caching strategy:

• fetch requests no longer cached by default
• More explicit cache control with unstable_cache
• Better cache invalidation with revalidateTag

Async Request APIs

Request-based APIs moved to async:

// Before (Next.js 14)
const params = useParams();

// After (Next.js 15+)
const params = await props.params;

Server Actions Improvements

Server Actions received significant upgrades:

• Better TypeScript inference
• Improved error handling
• Progressive enhancement support
• Form status with useFormStatus

Partial Prerendering (PPR)

The experimental PPR feature combines:

• Static shell rendered at build time
• Dynamic content streamed on request
• Best of both SSG and SSR

Middleware Improvements

• Better Edge Runtime compatibility
• Improved request/response manipulation
• Chained middleware support

Migration Tips

1. Update your next.config.js to next.config.ts
2. Review and update caching strategies
3. Migrate to async request APIs
4. Test with Turbopack in development

Conclusion

Next.js 15 set the foundation for the modern Next.js experience. If you're still on Next.js 14, upgrading is worth it for the performance improvements alone.

Sources

• Next.js 15 Release Notes
• Turbopack Documentation
• React Server Components
• Partial Prerendering
• Next.js Middleware