-
Notifications
You must be signed in to change notification settings - Fork 1.1k
middleware/proxy fixes for next.js 15/16 #9631
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
leoortizz
wants to merge
16
commits into
main
Choose a base branch
from
leoortizz_nextjsproxyfixes
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
16 commits
Select commit
Hold shift + click to select a range
5728b12
middleware/proxy fixes for next.js 15/16
leoortizz c7a59fa
Merge branch 'main' into leoortizz_nextjsproxyfixes
leoortizz f66edfe
changelog
leoortizz 6afc826
Merge branch 'main' into leoortizz_nextjsproxyfixes
leoortizz 5cb5555
Merge branch 'main' into leoortizz_nextjsproxyfixes
leoortizz 4e0b90b
check src directory
leoortizz 8cf8a3a
document middleware check in dev mode
leoortizz ba19ea4
update middleware types docs
leoortizz 10b3e21
Apply suggestion from @leoortizz
leoortizz 077c3db
remove extra space
leoortizz 02cb654
Merge branch 'main' into leoortizz_nextjsproxyfixes
leoortizz 64501f1
Merge branch 'main' into leoortizz_nextjsproxyfixes
leoortizz 0b3bf10
Merge branch 'main' into leoortizz_nextjsproxyfixes
leoortizz 06a9e1f
Merge branch 'main' into leoortizz_nextjsproxyfixes
leoortizz 12b6303
Merge branch 'main' into leoortizz_nextjsproxyfixes
leoortizz 46cd958
Merge branch 'main' into leoortizz_nextjsproxyfixes
leoortizz File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Some comments aren't visible on the classic Files Changed page.
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,4 +1,5 @@ | ||
| - Fixed pricing calculation for Cloud Functions deployed to newer regions (africa-south1, europe-west8, me-west1, and others) when using minInstances. (#9696) | ||
| - Removed MCP tools and prompts that required Gemini in Firebase terms of service. | ||
| - Fixes an issue where the `--only` flag was not always respected for `firebase mcp` | ||
| - Fix proxy.js/proxy.ts in Next.js 16 (#9631) | ||
| - Removed timeout when connecting to Cloud SQL. Hopefully, should mitigate issue #9314. (#9725) |
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
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
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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 was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are there reasonable more descriptive names that could be used instead of V1 or V3?
Are these all just different manifest types introduced at different nextjs versions?
For example could MiddlewareManifestNext16 or something work for MiddlewareManifestV3 ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ah nvm, these are literally the versions on the interface itself.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually, would we some day remove support for very old nextjs versions? In which case would some of these manifest versions would no longer be needed? could those versions be in the docstrings for MiddlewareManifestv2 and v1 ?
I think the "Middleware manifest types for Next.js 16" you added for v3 is very helpful.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Deferring to @jamesdaniels, but I don't think we would remove support for old Next.js versions as they just work?
The manifests won't be needed anymore as soon as we migrate to use the Adapters API. That's also why I chose to copy the V3 types instead of bumping the Next.js dependency, as it would require more changes that would not be necessary when we switch to the Adapters API.
The version of manifests does not match the Next.js version necessarily. I updated the comments to say in which versions they were used. I realized the manifest-middleware version 3 changed in Next.js 14.2.0, so I updated the comment. It's just that in Next.js 16 the proxy route matchers are in functions-config-manifest instead.