Make Server Function logging opt-in via logging.serverFunctions
#89321
+76
−2
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
nextjs-bot
added
created-by: Next.js team
Collaborator
Tests Passed |
Collaborator
Stats from current PR✅ No significant changes detected📊 All Metrics📖 Metrics GlossaryDev Server Metrics:
Build Metrics:
Change Thresholds:
⚡ Dev Server
📦 Dev Server (Webpack) (Legacy)📦 Dev Server (Webpack)
⚡ Production Builds
📦 Production Builds (Webpack) (Legacy)📦 Production Builds (Webpack)
📦 Bundle SizesBundle Sizes⚡ TurbopackClient Main Bundles: **434 kB** → **434 kB** ✅ -2 B81 files with content-based hashes (individual files not comparable between builds) Server Middleware
Build DetailsBuild Manifests
📦 WebpackClient Main Bundles
Polyfills
Pages
Server Edge SSR
Middleware
Build DetailsBuild Manifests
Build Cache
🔄 Shared (bundler-independent)Runtimes
📝 Changed Files (5 files)Files with changes:
View diffsapp-page-exp..ntime.dev.jsDiff too large to display app-page-tur..ntime.dev.jsDiff too large to display app-page-tur..ntime.dev.jsDiff too large to display app-page.runtime.dev.jsDiff too large to display server.runtime.prod.jsDiff too large to display |
eps1lon
approved these changes
Feb 2, 2026
Server Function logging (#88277) is now opt-in, consistent with how fetch logging works. This reduces noise in development logs by default. Additionally, for `'use cache'` Server Functions called from the client, the logging needs more work to be useful. Keeping it opt-in avoids exposing incomplete functionality by default. Server Function logging can be enabled in `next.config.js`: ```js module.exports = { logging: { serverFunctions: true, }, } ```
unstubbable
force-pushed
the
hl/opt-in-server-function-logging
branch
from
89b835f to
113e7fc
Compare
unstubbable
force-pushed
the
hl/opt-in-server-function-logging
branch
from
113e7fc to
fd40f37
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Server Function logging (#88277) is now opt-in, consistent with how fetch logging works. This reduces noise in development logs by default.
Additionally, for
'use cache'Server Functions called from the client, the logging needs more work to be useful. Keeping it opt-in avoids exposing incomplete functionality by default.Server Function logging can be enabled in
next.config.js: