fix: pass dotfiles option to serve-static#4
Merged
Julien-R44 merged 2 commits into2.xfrom Mar 15, 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
1 participant
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.
Close #3
Map
dotFiles( camelCase) todotfiles(lowercase) expected by serve-static/sendthe casing mismatch has always been there =>
dotFileswas never actually passed toserve-static, which expectsdotfilesbut nobody noticed because send v0.x (used by serve-static v1) had a legacy fallback: when
dotfileswas undefined, it would still allow requests to files nested inside dotfile directories (like/.well-known/stuff) , only blocking direct dotfiles (like/.env). so the.well-knownuse case worked by accidentwith the bump to serve-static v2 / send v1, that legacy fallback was removed. now when dotfiles is undefined, it defaults to 'ignore' for everything including dotfile directories