Remove deploymentId from App Router RenderOptsPartial#88866
Merged
Conversation
renderOpts instead
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: **432 kB** → **432 kB** ✅ -61 B82 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 (11 files)Files with changes:
View diffsapp-page-exp..ntime.dev.jsfailed to diffapp-page-exp..time.prod.jsDiff too large to display app-page-tur..ntime.dev.jsfailed to diffapp-page-tur..time.prod.jsDiff too large to display app-page-tur..ntime.dev.jsfailed to diffapp-page-tur..time.prod.jsDiff too large to display app-page.runtime.dev.jsfailed to diffapp-page.runtime.prod.jsDiff too large to display pages-api-tu..time.prod.jsDiff too large to display pages-turbo...time.prod.jsDiff too large to display server.runtime.prod.jsDiff too large to display |
Collaborator
Tests Passed |
lukesandberg
approved these changes
Jan 22, 2026
17cbfdd to
d90c506
Compare
renderOpts insteaddeploymentId from App Router RenderOptsPartial
wyattjoh
approved these changes
Jan 22, 2026
eps1lon
reviewed
Jan 22, 2026
Comment on lines
307
to
+309
| * The deployment ID if the user is deploying to a platform that provides one. | ||
| */ | ||
| deploymentId: string | undefined | ||
| deploymentId: string |
Member
There was a problem hiding this comment.
Does that JSDoc still make sense? What's the expected value/type if the platform doesn't provide a deployment ID?
Member
Author
There was a problem hiding this comment.
In 90% of the codebase, it's represented as an empty string in that case.
next.js/packages/next/src/server/base-server.ts
Lines 466 to 468 in 9e97759
Ideally, we'd make it consistently use
string | undefined everywhere as opposed to "string or empty string"
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.

There should only be a single place for it now (
ctx.sharedContext.deploymentId)