#106: shadcn Registry, next-seo, Page Transition Strategies, Directives Drama, next-lens, Backends on Vercel

Next.js Conf 2025 session VODs are live – All sessions from this year’s Next.js Conf are now live! Tons of great ones this year. I’d personally recommend:

• ► Hands on: How to migrate to Next.js 16 and "use cache”
• ► Composition, Caching, and Architecture in Modern Next.js
• ► Type-safe URL state in Next.js with nuqs
• ► Reactive State for the Backend

𝕏 Backends on Vercel – Guillermo highlights improvements in function runtime, cost control, Python support, and AI‑ready features like Sandbox and AI Gateway. All part of the mission to make Vercel just as strong for backends as it’s known to be for frontends.

Build international Next.js apps with confidence – Master the art of holistic internationalization, from the fundamentals to advanced patterns, all through a real-world project. Now 25% off for subscribers of Next.js Weekly!

Zero configuration Next.js deployment to a self hosted VPS – The post covers installing Kamal, configuring Docker, fixing build issues, and setting up health checks so your app deploys smoothly.

Comparing Page Transition Strategies in Next.js – A detailed side-by-side test of six navigation methods in Next.js, from old-style full-page reloads to modern setups using Speculation Rules and CSS View Transitions.

►This is good, actually – Theo thinks directives like “use workflow” are a clever way to handle complex serverless problems with less fuss, pushing back on critics like Tanner Linsley, who say they’re confusing and not standard (linked further down).

Tried React 19’s Activity Component: Here’s What I Learned – Roy argues how the new <Activity> component fills a long-missing gap in React: being able to hide a component without unmounting or bogging down your app.

shadcn Registry Directory – shadcn dropped a list of code registries you can browse and pull code or components from. If you're a registry maintainer and want to add yours to the directory, just fill out the following issue.

next-lens – next-lens brings a “Laravel artisan” experience to your terminal. It scans your app structure, detects route handlers, and displays clear, color-coded tables of your pages and APIs.

next-seo v7.0.0 – A plugin that makes managing your SEO easier in Next.js projects. This new version is a full rewrite with major API changes. All structured data components were rebuilt to fully follow Google’s latest schema standards. Migration guides are available, but most setups will need a full refactor.

aws-workflow – AWS adapter for the Workflow Devkit that was introduced at Vercel Ship AI last week. Check out the tweet if you want to see a demo.

More:

• c15t v1.7.0 Developer-First Consent Banner – Script Loader & iFrame Blocking
• Vercel Deployments menu bar app (Linux) – Linux alternative to the macOS version that was featured in the last issue

Escape the vendor-locked in edge-runtime! Try Sevalla with $50 credit now. Your PaaS from the future – Prefer the power of a full Node.js environment? Get lower bandwidth costs and predictable pricing combined with real human support by developers. No seats, no surprise serverless bills. Ever.

Understanding Directives – Explains the thinking behind Workflow DevKit’s directive system. It describes how the team experimented with different API designs before deciding that plain JavaScript directives were the clearest and safest way to mark workflow and step functions.

React vs. Backbone in 2025 – This opinion-piece compares the code of a simple password strength test app built with React and Backbone, and finds that after 15 years of progress, both do the same job with similar amounts of code. The author argues that modern abstractions aren’t always simpler, and maybe we’ve traded genuine clarity for the illusion of simplicity.

Directives and the Platform Boundary – Explains that new directives like use client and use server make framework features look like real JavaScript. This makes it harder for developers and tools to know what’s part of the language and what’s not. The author suggests using normal APIs with imports instead to make ownership clear and keep the platform boundary clean.