-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
fix(start-server-core): bump h3 from v2.0.1-rc.2 to v2.0.1-rc.6 #6161
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
Merged
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
a260153
h3 v2 rc 6
birkskyum ddaa6a3
Merge branch 'main' into h3-rc.6
birkskyum fa6f754
fix(start-server-core): maintain behavior of set-cookie in redirects
birkskyum b9a589b
cleanup
birkskyum e5582da
Merge branch 'main' into h3-rc.6
birkskyum bc6b53f
lint
birkskyum 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
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
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
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
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.
🧩 Analysis chain
🏁 Script executed:
Repository: TanStack/router
Length of output: 111
🏁 Script executed:
Repository: TanStack/router
Length of output: 1105
🏁 Script executed:
cat -n packages/start-server-core/src/request-response.ts | head -50Repository: TanStack/router
Length of output: 1870
🏁 Script executed:
Repository: TanStack/router
Length of output: 1509
Response headers mutation will fail at runtime for immutable Response objects.
The code directly mutates
response.headersusingdelete()andappend(). However, Fetch API Response headers are immutable when created via Response.error(), Response.redirect(), or received from fetch(), throwing a TypeError if mutation is attempted. Since themergeEventResponseHeadersfunction receives a generic Response parameter with unknown origin, this approach will fail for responses with immutable headers.Instead of mutating headers directly, create a new Response with merged headers:
Alternatively, check if headers are mutable before attempting mutation, with fallback to response reconstruction for immutable headers.
🤖 Prompt for AI Agents