Stable Next.js Adapters, WebSocket in App Router, AI Improvements, Error Handling, Sugar High, transitionType prop
Next.js Across Platforms: Adapters, OpenNext, and Our Commitments
Next.js now has an official, stable way for hosting platforms to support the framework. The new Adapter API describes your app's build output in a typed, versioned format that any provider can target. Vercel uses the same public API as everyone else, and a shared test suite ensures consistent behavior across platforms
AI Improvements
This post was part of the Next.js 16.2 release. It focuses on making Next.js work better with AI coding agents. New projects now include an AGENTS.md file that points agents to bundled docs, browser errors get forwarded to the terminal, a lock file stops duplicate dev servers, and an experimental CLI lets agents inspect your running app through the terminal
⚡️ Sponsor
Core 3: Clerk's biggest SDK release yet, built for Next.js
Core 3 ships major improvements for Next.js developers: @clerk/nextjs now sheds ~50KB gzipped by sharing React across SDKs, concurrent rendering and streaming SSR work correctly with Clerk's auth state, and satellite domains skip unnecessary redirects for anonymous visitors. New hooks replace Clerk Elements for custom sign-in and sign-up flows. Upgrade with one CLI command.
📙 Articles / Tutorials / News
Error Handling in Next.js with catchError
Aurora Scharff explains why react-error-boundary falls short with Server Components, and how unstable_catchError in Next.js 16.2 fixes it by handling framework errors correctly and re-fetching server data on retry
Making sense of 'key' prop in react
Walks through reconciliation, shows how missing or bad keys cause state bugs, and explains what makes a key actually useful
PR: add WebSocket support for App Router route handlers
A new PR adds native WebSocket support to route handlers via NextResponse.upgrade(). It follows the standard WebSocket interface, works with middleware for headers, rewrites, and redirects
𝕏 React didn’t invent RSC, SSR, or Hydration
Shu Ding shows how SSR, RSC, and Hydration map directly to older tools like Express, Pug, and jQuery
𝕏 transitionType prop for Links in Next.js 16.2
Demonstrates how to set the transition type (e.g. fade, slide-left, etc.) of the ViewTransition for a link
📦 Projects / Packages / Tools
TypeScript 6.0
The last version built on the JavaScript codebase. It's a transition release designed to prepare you for TypeScript 7.0, which is being rewritten in Go for much better performance. New features include Temporal API types, RegExp.escape, and Map.getOrInsert. There are also some breaking changes
Next.js Native App Template
A boilerplate for building native-feeling PWAs with Next.js 16. Ships as a workout tracker but is designed to be swapped with your own app. Handles all the tricky iOS PWA quirks like broken fixed navs and scroll issues so you don't have to
Apiser
Gives you a higher-level way to work with Drizzle by wrapping tables in models with chainable queries, relation loading, result shaping, and safe error handling
Sugar High
Super lightweight code syntax highlighter, around 1KB after minified and gzipped
⚡️ Sponsor: Expo
How to go from Web to Native with React
Everything that web devs need to know about building their first mobile app - You already know React. With Expo, you can use that knowledge to build fully native apps for iOS and Android without starting over or learning new tools
🌈 Related
A React trick to improve exit animations
Components that update mid-exit-animation look janky. This trick wraps exiting components in Suspense to freeze their DOM, preventing any visual changes during the animation
How to Measure and Optimize React Performance
Learn to use React 19.2s Performance Tracks and DevTools Profiler to find problems, then apply runtime optimizations, concurrency features, and build-time tools to solve them
Start naming your useEffect functions, you will thank me later
The post argues that named useEffect functions make React code much easier to understand and can also reveal effects that are doing too much
Making React ProseMirror really, really fast
React ProseMirror was too slow for large documents. A single keypress in Moby Dick took 177ms. Through memoization and ref-based position tracking, they got it down to 16ms, even beating ProseMirror's native rendering on Firefox
Have a link you want to share? Send me an email at erfan@nextjsweekly.com
All submissions are appreciated.
👋 See you next week!