# vercel/next.js · RepoSense Release & Migration Intelligence

> Persist Request Insights session history: #97795. Pre-release build; test in staging. Migration: Low.

## Metadata
- **Repository URL**: https://github.com/vercel/next.js
- **Primary Package**: `next` (NPM)
- **Categories**: `FRAMEWORK`, `BACKEND`
- **Latest Version**: `v16.5.0-canary.42`
- **Semantic Status**: `WARNING`
- **Bundle Size Impact (unavailable)**: `Size Unavailable`
- **Atom Ingestion Feed**: https://github.com/vercel/next.js/releases.atom

## The Human Context (Plain-English Pitch)
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.

## Stage 1 Executive Summary ([Core Change] + [Required Action] + [Migration Effort])
Persist Request Insights session history: #97795. Pre-release build; test in staging. Migration: Low.

## Breaking Changes & Required Actions
- 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

## Migration Snippet
```ts
npm install next@16.5.0-canary.42
```

## Ecosystem Compatibility Matrix & Graph Warnings
- **TypeScript 5.x** [`COMPATIBLE`]: Ships standard TypeScript declaration files without type regressions.
- **Graph Conflict (next ↔ @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. | Resolution: `npm install next@16.5.0-canary.42 @tanstack/react-query@@tanstack/vue-query-devtools@6.3.11`

## Zero-Noise Release Timeline
- **v16.5.0-canary.42** (2026-11-05) [WARNING]: Persist Request Insights session history: #97795. Pre-release build; test in staging. Migration: Low.

## Upgrade & Migration Q&A (GEO Direct Answers)
### Is 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