test: stabilize fetch fixtures and update JS tooling#75
Merged
Conversation
Merging this PR will not alter performance
Comparing Footnotes
|
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
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.
What changed
fallowto 3.5.0,oxfmtto 0.59.0, andoxlintto 1.74.0Why
The JavaScript tooling had newer releases available. Windows CI also intermittently reset local fixture connections because the test server closed sockets while request headers remained unread. That could prevent the client from making the expected second request and leave the server waiting until its accept timeout.
The fixture now waits for the complete HTTP header terminator before responding. Production fetch behavior is unchanged, and no new runtime or test dependency is introduced.
Validation
pnpm checkpnpm test