Turbopack: don't generate next-server.js.nft.json with adapters#93684
Open
Turbopack: don't generate next-server.js.nft.json with adapters#93684
Conversation
github-actions
Bot
added
created-by: Turbopack team
![vercel[bot]](https://avatars.githubusercontent.com/in/8329?s=60&v=4){kind=small}
| @@ -0,0 +1,4 @@ | |||
| /** @type {import("next").NextConfig} */ | |||
Contributor
There was a problem hiding this comment.
Adding next.config.js to the test/production/next-server-nft/ directory causes the "with output:standalone" test suite to crash because it provides both a next.config.js file (via files: __dirname) and a nextConfig option, which the test framework explicitly forbids.
Contributor
There was a problem hiding this comment.
nextConfig provided on "createNext()" and as a file "next.config.js", use one or the other to continue
Contributor
There was a problem hiding this comment.
@lukesandberg Thanks for confirming — that's exactly the error the suggestion above addresses. The fix moves the output: 'standalone' setting into next.config.js via an env var (NEXT_OUTPUT_MODE), consistent with how adapterPath already uses NEXT_ADAPTER_PATH.
Contributor
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
Server Middleware
Build DetailsBuild Manifests
📦 WebpackClient Main Bundles
Polyfills
Pages
Server Edge SSR
Middleware
Build DetailsBuild Manifests
Build Cache
🔄 Shared (bundler-independent)Runtimes
📎 Tarball URLCommit: a60a1de |
Contributor
Failing test suitesCommit: a60a1de | About building and testing Next.js
Expand output● next-server-nft › with output:standalone › should not trace too many files in next-server.js.nft.json
Expand output● next-server-nft › with output:standalone › should not trace too many files in next-server.js.nft.json |
lukesandberg
approved these changes
May 8, 2026
Contributor
lukesandberg
left a comment
lukesandberg
left a comment
There was a problem hiding this comment.
vade comment is on point
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Adapters don't read these files.
Also added a snapshot test similar to the existing ones to not regress on function size