fix(nextjs): Avoid wrapping middleware files when in standalone mode #18172
+2
−1
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
Member
|
Did you test this one in the repro? |
Collaborator
Author
|
Yep, it builds the app correctly and we get the middleware spans. |
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
logaretm
force-pushed
the
awad/js-1079-sentry-causes-nextjs-16-build-to-fail-when-using-standalone
branch
from
b404968 to
ca164ec
Compare
3 tasks
logaretm
force-pushed
the
awad/js-1079-sentry-causes-nextjs-16-build-to-fail-when-using-standalone
branch
from
ca164ec to
bf7e473
Compare
logaretm
changed the title
chargome
approved these changes
Nov 12, 2025
logaretm
deleted the
awad/js-1079-sentry-causes-nextjs-16-build-to-fail-when-using-standalone
branch
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.
This PR attempts to fix #18001 by not wrapping the middleware files if Next.js 16 is the current version and is in standalone output mode which is the problematic scenario.
Investigation:
proxytomiddlewareunder the hood.proxy.jsentry is produced inmiddleware.js.nft.jsonwhich wouldn't be there otherwise, meaning if we don't wrap it then that entry doesn't get produced. So it seems like@vercel/nftis somehow adding theproxyfile as a dependency of itself which fails to copy to the output directory because it was already copied and renamed toproxy.jsor at least that is what I'm guessing is happening.