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
Transcript
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 opt-in approach was overly conservative. Users can still disable it by setting `serverFunctions: false` in their next.config.js.
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 production test manifests for Rspack integration, and a backport was applied to ensure server actions transform properly in node_modules for route handlers.
What's next: Watch for improvements to cache function logging output and continued webpack build optimization work.
That's your Next.js update for February 3rd. We'll be back tomorrow with more development news.