Repository navigation
docs: align README examples with v3 match results - #115
Merged
blakeembrey merged 1 commit intoOct 30, 2026
Merged
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
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.
After #109, TypeIs returns the original configured string. The README body-parser example still switches on normalized MIME types, so requests for all three configured types fall through to HTTP 415.
Update the switch cases and the
request()return-value example to preserve the configured shorthands, and explain that return contract. Also use explicit named ESM imports in the examples to match the v3 exports.Validation on upstream
f61fd0318c775d8e4a9590143eb92487c23afe58, Windows, Node 24.12.0:text/plainstill returns 415, and a bodyless GET still calls the next handler. The harness resolves imports locally and catches the example's intentionalimplement ... parsingerrors to identify the selected branch; it does not implement body parsing.request()results: one mismatch before, all correct afterward. Checked the named imports and all fivematch()examples against the built module.npm test: passes, including build, Prettier, typechecking, and all 311 tests.git diff --checkpasses.Documentation only. Implementation and verification assisted by Codex.