Next.js Daily: Server Function Logging Updates and Build Fixes

The Next.js team made significant changes to Server Function logging configuration, switching from opt-in to default-enabled with exceptions for cache functions. Build tracing for webpack was also restored after being removed in a previous update.

Duration: PT1M39S

Episode overview

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

It explains recent repository work in plain language.

  • Show: Next.js Daily
  • Published: 2026-02-03T11:17:04Z
  • Audio duration: PT1M39S

Transcript excerpt

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

Good morning, it's February 3rd, 2026. I'm your host with today's Next.js development update.

The main story today involves Server Function logging. Hendrik Liebau first made Server Function logging opt-in via a new `logging.serverFunctions` configuration option to reduce development noise. However, this was quickly reversed in a follow-up merge that restored default-enabled logging, determining the original…

A third related change disabled Server Function logging specifically for 'use cache' functions called from the client, as the current output shows internal implementation details rather than useful function names.

JJ Kasper merged a partial revert that restored build-complete traces for webpack. This addresses issues from a previous change that removed necessary tracing functionality, ensuring proper webpack build monitoring continues to work.

On the documentation front, several small improvements landed: Jan Amann fixed broken code snippets in the custom server guide, Joseph added multi-package manager syntax for the experimental analyze command, and Pavan Shinde standardized "cannot" usage across documentation files.

The Vercel release bot updated both development and…

Nearby episodes from Next.js Daily

  1. Server Action Optimization and Turbopack Performance
  2. React Upgrade and Instant Validation
  3. Instant Navigation Testing API Launch
  4. Turbopack Enhancements and React Updates
  5. Canary Release Bump
  6. Turbopack Enhancements and Cache System Updates
  7. Cache Optimization and Security Updates
  8. React Updates and Feature Rollbacks