Tag
Every post tagged Next.js.
Next.js & React
A tested Sign-In with Ethereum flow for Next.js 16 with viem and iron-session: nonce, wallet signature and session, plus the cookie-nonce replay bug and the 1-second default verify I found while attacking it.
AI Engineering
How Benchline runs 61 browser tools where each one is a pure function shared by a web page, a stateless Streamable HTTP MCP server and a JSON API, using real code from the repo.
AI Engineering
I upgraded a real AI SDK 6 app to AI SDK 7. The codemod fixed 15 lines in 20 seconds but only 1 of 9 broken tests. Here's every step, the behaviour changes TypeScript misses, and the OpenTelemetry trap.
Next.js & React
TanStack Start 1.0 is stable, so I built the same store in Start and Next.js 16.4 and benchmarked both. Start served 2.9× to 8.6× more dynamic requests, shipped 20% less JS and built 3.9× faster. Next.js won on static pages.
Developer Tools
I ran ESLint 9 and 10, Oxlint 1.88 and Biome 2.5 on this site's real Next.js code. Oxlint was 81× faster than ESLint with the same rules and matched all 80 typescript-eslint findings 16× faster. Here's what each migration keeps and breaks.
Next.js & React
I compiled a Next.js 16.4 app with no compiler, the Babel React Compiler and the new Rust React Compiler, then counted re-renders in Chrome: 20,000 row renders dropped to 0, build cost, bundle size, lint rules and the memo() gap.
Next.js & React
A tested Better Auth 1.7 setup for Next.js 16.4 with Prisma 7 and PostgreSQL: route handler, server-action sign-in with nextCookies, proxy.ts checks, query counts per page load, the joins gotcha and Better Auth vs Clerk.
Next.js & React
Drizzle vs Prisma, benchmarked on PostgreSQL 17 across Drizzle 0.45, Drizzle 1.0 RC, Prisma 7 and Prisma 8 RC: query speed, the OFFSET trap, cold starts, install size, migrations and which to choose.
Next.js & React
React View Transitions are stable in React 19.3 and work in Next.js 16.4 with no config. Shared-element morphs, Suspense reveals, directional slides and addTransitionType, tested in Chrome, plus the back-button gap.
