Next.js: The Server Function Logging Dance

Today's episode covers a fascinating back-and-forth in the Next.js codebase around Server Function logging defaults, plus some solid documentation improvements and build system refinements. We saw three related PRs that tell the story of finding the right balance between useful developer tools and clean console output, along with helpful community contributions fixing docs and improving the developer experience.

Duration: PT4M8S

Episode overview

This episode is a short developer briefing from Next.js.

It explains recent repository work in plain language.

  • Show: Next.js
  • Published: 2026-02-03T11:16:28Z
  • Audio duration: PT4M8S

Transcript excerpt

This excerpt keeps the crawler page concise. Listen to the episode or use the RSS feed for the full update.

Hey there, developers! Welcome back to another episode of the Next.js podcast. I'm your host, and wow, do we have an interesting story to tell today from the Next.js codebase. You know those moments when a team is really thoughtfully considering the developer experience? Well, we just witnessed one play out in real…

Let me paint you the picture. We had ten pull requests merge yesterday, and the most fascinating part is this trilogy of changes around Server Function logging that really shows how the Next.js team thinks about defaults and developer experience.

It all started with PR 89321 from unstubbable, who made Server Function logging opt-in via a new `logging.serverFunctions` config option. The reasoning was solid - they wanted to reduce noise in development logs by default, just like how fetch logging works. Makes sense, right? Less clutter in your terminal, cleaner…

But here's where it gets interesting. Just a few hours later, the same contributor submitted PR 89407 that completely reversed course! They restored Server Function logging to be enabled by default. And you know what? This wasn't a mistake or flip-flopping - it was thoughtful iteration. The team realized that the…

Now…

Nearby episodes from Next.js

  1. Performance Optimizations and Clean-up Day
  2. The Great Infrastructure Upgrade
  3. Instant Navigation and Smart Caching Get Major Upgrades
  4. Instant Navigation Revolution - New Testing APIs and Performance Breakthroughs
  5. Turbopack's Infrastructure Upgrade
  6. Rolling Forward with v16.2.0-canary.23
  7. Turbopack Takes Center Stage with Optional Support and Cache Performance Wins
  8. Cache Revolution & Security Hardening