🚨 New CVEs, Next.js Patterns & Best Practices, Github PRs UI with RSCs, next-lens, Inside Turbopack

► Next.js Patterns: Public pages with personalization (6:37)

Delba shows how to start with a fully static page and slowly add async and user-specific content without slowing things down

🚨 New Next.js CVEs

Several denial‑of‑service vulnerabilities were found that could crash servers or cause very high memory or CPU usage. The issues affect React Server Components and some self‑hosted Next.js setups under specific conditions. Fixes are available in the latest React and Next.js releases:

• CVE-2026-23864
• CVE-2025-59471 and CVE-2025-59472

---

⚡️ Sponsor

Clerk MCP Server for AI Coding Assistants

Connect the Clerk MCP server to your AI coding assistant for accurate authentication implementation patterns. Ask Claude or Cursor "How do I protect API routes?" and get current SDK snippets and best practices pulled directly from Clerk docs.

📙 Articles, Tutorials

Rebuilding a better GitHub PRs UI with Next.js and RSCs

Francisco Miranda built a faster GitHub pull request UI using Next.js and React Server Components. The project leans heavily on server rendering, minimal client components, Next.js caching, and Suspense to keep large PRs responsive

Next.js Image Optimization

A beginner-friendly breakdown of how Next.js handles images using the built-in next/image component. It covers topics such as how to avoid common mistakes like lazy-loading LCP images, preloading, blur placeholders, and when to consider alternatives like Unpic

Build a Next.js 16 PWA with true offline support

This guide goes beyond the basic PWA setup in Next.js. It shows how to build an offline-first app using service workers, IndexedDB, and sync logic, so users can add and update data without a connection and sync later

Next.js Glossary

Vercel launched a large, up-to-date glossary that explains common Next.js concepts in simple language, from App Router and Server Components to caching, streaming, and Turbopack

---

📦 Projects / Packages / Tools

next-best-practices

A new skill set from Vercel that helps agents follow best practices when working with the Next.js App Router. It covers concepts like Server and Client Components, data fetching, routing, performance, and error handling, and also includes optional skills for version upgrades and features like Cache Components

next-lens v1.2

next-lens has shipped several nice updates since the last time it was featured. The web inspector lets you browse routes visually, search and filter them, manage API methods, and open source files directly in your IDE. There’s also a new Raycast extension that lets you inspect routes, copy paths, and jump into your editor

json-render

A new library for building AI‑driven UIs using safe, predictable JSON instead of free‑form text. You can define a component catalog and allowed actions, then let AI stream JSON that always matches your schema.

next-seo v7.1.0

This release adds a new HowToJsonLd component that helps search engines understand your how‑to guides. You can describe steps, tools, materials, time needed, cost, and even videos in a clear, structured way

---

⚡️ Sponsor

Add Skills to your AI-SDK Agent in minutes

Execute Skills in runtime VMs without building infrastructure. Run complex scripts, read Skills on-demand, install dependencies, mint download links, and build predictable, specialised agents in minutes.

---

🌈 Related

Inside Turbopack: Building Faster by Building Less

Learn how the smart caching system behind Turbopack works, and how build results are reused and now saved to disk for faster restarts

The Incredible Overcomplexity of the Shadcn Radio Button

The author argues that modern UI libraries often rebuild basic browser features from scratch, even when native HTML and a bit of CSS would do the job better

Bun Is Fast, Until Latency Matters for Next.js Workloads

Interesting benchmark showing that while Bun is often seen as very fast, it struggles with latency in real Next.js server workloads. Under heavy traffic, Deno and Platformatic Watt had much lower and more stable response times, with Node.js in between.

I left frontend for SDET, then came back

A personal story about leaving frontend work to become an SDET, facing fears around CI, testing, and infrastructure, and why it ended up making the author a much better frontend developer