vercel/next.js
v16.5.0-canary.42The React Framework for the Web with App Router, Turbopack, and Partial Prerendering.
Next.js is a full-stack web framework built on top of React that handles routing, server-side rendering, and production bundling out of the box. It solves the headache of wiring together separate routers, build tools, and API servers so teams can ship fast, SEO-friendly web applications with zero configuration.
Persist Request Insights session history: #97795. Pre-release build; test in staging. Migration: Low.
Key Release Highlights (v16.5.0-canary.42)
- Persist Request Insights session history: #97795
- Show route module loading and preparation in Request Insights: #97362
- Improve Request Insights request and fetch details: #96925
- Automatically compress route handler responses if not already compressed: #101220
Experimental pre-release build (v16.5.0-canary.42) for next. Test in staging or CI environments before promoting to production.
npm install next@16.5.0-canary.42Ecosystem Compatibility Matrix & Verified Graph Warnings
Verified BREAKS_WITH Graph Edges
Next.js 15.2 enforces async headers() and cookies() in RSC, throwing hydration context errors in @tanstack/react-query <5.64.0. Upgrade @tanstack/react-query to ^5.66.0 before bumping next. Migration: Low.
npm install next@16.5.0-canary.42 @tanstack/react-query@@tanstack/vue-query-devtools@6.3.11Zero-Noise Historical Release Timeline (1)
Format: [Core Change] + [Required Action] + [Migration Effort]Persist Request Insights session history: #97795. Pre-release build; test in staging. Migration: Low.
Upgrade & Migration Q&A (vercel/next.js v16.5.0-canary.42)
Direct Answers for Engineers & AI AgentsIs vercel/next.js v16.5.0-canary.42 safe to upgrade in production?
vercel/next.js v16.5.0-canary.42 is classified as WARNING (PRERELEASE release). Persist Request Insights session history: #97795. Pre-release build; test in staging. Migration: Low.
What breaking changes or compatibility risks exist in vercel/next.js v16.5.0-canary.42?
next with @tanstack/react-query: Next.js 15.2 enforces async headers() and cookies() in RSC, throwing hydration context errors in @tanstack/react-query <5.64.0. Upgrade @tanstack/react-query to ^5.66.0 before bumping next. Migration: Low.
What is the bundle size impact of next v16.5.0-canary.42?
Measured bundle size telemetry is currently unavailable for next v16.5.0-canary.42; verify build output locally before deploying.
How do I upgrade next to v16.5.0-canary.42?
Upgrade next to v16.5.0-canary.42 by running "npm install next@16.5.0-canary.42" and applying the migration steps: npm install next@16.5.0-canary.42