A Next.js release for the boys

Today’s issue: Signing the (second) most important document in American history, keeping your secrets safe from AI, and why I have mixed feelings about PETA’s latest campaign.

Welcome to #509.

---

A Next.js release for the boys

It’s been such a quiet year for Next.js—you know, except for the RSC vulns that (maybe) sent Sebastian Markbåge into retirement. But apparently, the React / Next core team is like the Hydra because when it loses one member, two former members return to take their place (welcome back, Dan and Pete). Needless to say, this week’s Next 16.3 release was a sight for sore eyes.

Now that companies, including Vercel, are investing heavily in winning the agent framework battle, it’s fair to question what we can expect from front-end frameworks moving forward. And this release, at least in part, answered some of those questions. For now, it seems like Next is still trying to make good on some of the promises that were made back in 2020, while also making things better for the humans and agents working with the framework.

Let’s take a look at some of the highlights.

• Instant Navigation: With Server Components, one of the byproducts of moving data fetching to the server was that client navigations felt unresponsive. Now, by setting cacheComponents: true in your Next config, every await on the backend will either suspend (showing your loader) and stream in the UI, or return the cached version of the page until the new data loads. They also added better support for prefetching to enable an “SPA-like experience” when using RSC.

• Better AI Tooling: In addition to shipping an officially maintained set of skills for Next that scold your agent for using outdated practices, the team included a feature they are calling “Instant Insights,” which detects caching errors and gives you a prompt for your agent to fix them. They also added a new tool to help you better understand how your customers will experience navigations in production.

• Improved Dev Server: The dev server now uses 90% less memory for long-running sessions. It also uses TypeScript 7, which speeds up type-checking, and the latest version of Turbopack, which has experimental support for the Rust-based React compiler.

Bottom Line: Getting the band back together to try and finish Server Components before the singularity is true dedication to an idea no one is convinced is worth it. But that’s what makes this release all the more special.

---

Cut code review time & bugs in half, instantly

AI code reviews are an essential tool for every software team, but what sets CodeRabbit apart is the speed and quality of its reviews. That’s why customers like NVIDIA and open-source projects like Bun rely on it.

Here’s how CodeRabbit helps teams ship faster:

• Fast and accurate reviews: Codegraph and custom guidelines help it understand complex dependencies across files and uncover the impact of your changes.

• Self-improving: Set the baseline with your rules and style guides, then train the agent with feedback via replies and watch its reviews improve over time.

• Architected for security: In addition to being SOC 2 certified and using SSL encryption for data in transit, CodeRabbit is architected to keep your code safe and secure.

Try CodeRabbit today.

---

1. Steve Yegge wrote about how GPUs have feelings in his latest essay. Not sure how I’m gonna feel when I see the PETA (People for the Ethical Treatment of Agents) campaigns start to hit the TL.

2. Theo Ephraim built a tool called Varlock that makes your .env files AI-safe without breaking your app.

3. Sentry is teaming up with Etsy to put on a free workshop about how to stay crash-free during traffic spikes. [sponsored]

4. Kirupa built some interactive labs to help you understand the cost of DFS and BFS algorithms.

5. Paolo Perrone crunched the numbers on whether you should self-host your own inference stack or rent from the overlords.

6. Cloudflare is giving agents their own computers (isolate + container + browser + virtual file system). My agent prefers using a Mac (at least that’s what they told me).

7. Miranda Heath wrote a report on burnout in open source, which includes powerful stories from maintainers and structural ways to avoid burnout. [sponsored]

8. 1,346 employees at frontier AI companies (including Ilya and Dario) signed a statement saying that we need to slow the pace of AI development. I also signed on behalf of Fireship.

9. Adeel Raza created an open-source React image editor that lets you crop and resize images, draw shapes, and more.

10. David and Peli wrote about how they automated documentation updates across repos using GitHub Agentic Workflows. I get it… there are only so many times a developer can be asked “where are the docs?” before they snap.