AI summary by TwinMind
Next.js 15 Is Here (Vercel Ship Breakdown)
Theo - t3․gg
19m 33s
Vercel Ship Event Overview
- Event covered Next.js 15 RC, Vercel Firewall, AI features, and other announcements
- Video created on creator's day off due to importance of updates
- Disclaimer: Not sponsored content, genuine analysis without Vercel approval
Vercel Firewall Launch
- Addresses overdue need for DDoS protection without CloudFlare
- CloudFlare CDN in front of Vercel historically caused caching issues
- Provides ability to set up rules preventing website destruction and massive bills
- Looks promising based on blog post review
Feature Flags Rethought
- Shouted out Jane Wong for feature flag leaking expertise
- Twitch example: Feature flags exposed in client-side experiments object
- Problem: Client-side feature flags allow users to see all unreleased features
- Solution: Vercel building server-side feature flags to prevent client exposure
- CTO reports positive experience with new implementation
Next.js 15 RC Details
- RC status due to React 19 dependency, not readiness issues
- Expected to become official release within hours/minutes of React 19 launch
- Install via:
npm install next@rcorcreate-next-app@rc
React 19 Integration
- App router built on React Canary channels for frameworks
- Next.js ignores package.json React version, loads required version
- React 19 shipping will end version confusion
- Supports React 19 RC with client/server actions
React Compiler Support
- Technically works in React 18 but not recommended
- React 19 provides proper support without weird polyfills
- Simple adoption: Two config changes in Next.js RC
- Performance improvements observed (benchmarks pending)
- Requires ESLint rules for proper optimization
- Annotation mode available with @memo directive
Hydration Error Improvements
- Started in 14.1, significantly improved in 15
- Now shows actual diffs between client/server rendering
- Example: "P class name was 'paragraph' on client but 'text' on server"
- Common causes: Date.now(), typeof window checks
- Makes debugging complex hydration errors much easier
Caching System Overhaul
- Killed aggressive default caching that upset community
- fetch() no longer cached by default
- Pages no longer cached by default
- GET route handlers no longer cached by default (previously insane behavior)
- Example: GET endpoint returning
new Date().toLocalString()was cached at build time - Client router cache no longer caches page components by default
- Loading files remain cached for 5 minutes
- Opt-in caching via web standard
cache: 'force-cache'option - Multiple configuration options for different caching needs
Partial Pre-rendering (PPR) Improvements
- Incremental adoption now possible (previously all-or-nothing)
- Can enable PPR on specific routes instead of entire app
- Benefits: Static shell served immediately, dynamic content streams later
- Addresses cold start penalties (300ms-1s) for Lambda-based apps
- Ideal for homepage, terms of service, blog posts while keeping other pages dynamic
unstable_after API
- Allows work to be queued after response is sent
- Prevents Lambda death before completion of post-response tasks
- Use cases: Analytics, logging, Sentry data, PostHog tracking
- Contribution by Lu (Janka) - early server components advocate
- Game-changer for non-blocking analytics and logging
Create Next App Template Redesign
- Removed excessive blue gradient and complex styling
- Reduced from 115 lines to more minimal template
- Cleaner, less overwhelming starting point
- Still includes some Tailwind but significantly reduced
- Turbo pack option now available during setup process
Turbo Pack Progress
- Dev mode: All tests passing, ready for developer use
- Production mode: Only 82.6% of tests passing
- Prompted during create-next-app setup
- Default expected by Next.js 16 (not 15)
- Faith in Rust rewrite project slowly dwindling due to extended timeline
Performance Optimizations
- External package bundling improved in app router
- Server external package config option added
- Pages router performance improvements included
- V8 bytecode caching on Vercel infrastructure
- Reduces cold start times and improves response times
- Challenges current serverless approaches
Pages Router Support
- Continues to receive performance improvements
- Not being abandoned despite app router focus
- Server rendering performance improvements included
- Vercel confirms ongoing support commitment
