docs: resolve.fileSystem is honored since webpack 5.111.0 - #8402
Merged
Merged
Conversation
webpack/webpack#22091 stopped webpack from assigning the compiler's input filesystem over a configured resolve.fileSystem, so the page's warning that setting it has no effect is true only up to 5.110.x. Documents the option as it now behaves, keeps the older workaround as a version note, and says what still goes through the compiler's inputFileSystem.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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.
Summary
webpack/webpack#22091 has landed, so webpack no longer assigns the compiler's input filesystem over a configured
resolve.fileSystem. The page currently warns that setting the option has no effect, which was accurate up to 5.110.x and is wrong from 5.111.0 on. Documents the option as it now behaves, keeps the old workaround as a version note for anyone on an earlier release, and adds the boundary the option does not cross: resolution reads through it, module source still reads through the compiler'sinputFileSystem. Also updatesresolve.resolver, which told readers a whole resolver was the only way to reach a different filesystem from the configuration.Verified against the merged
main(00c73f0a): with a counting filesystem in the config, resolution made 32 calls throughresolve.fileSystemand 23 throughresolveLoader.fileSystem, and a second probe showed the resolver readingpackage.jsonthrough the configured filesystem whilesrc/index.jswas read through the compiler's. 5.111.0 is the version 18 pending minor changesets put on top of 5.110.3.What kind of change does this PR introduce?
docs
Did you add tests for your changes?
n/a — documentation only; the behavior it describes is covered by
test/configCases/resolve/custom-file-systemin webpack/webpack#22091.Does this PR introduce a breaking change?
No.
If relevant, what needs to be documented once your changes are merged or what have you already documented?
n/a — this PR is the documentation follow-up for webpack/webpack#22091.
Use of AI
AI was used. Claude Code ran the probes quoted above against the merged webpack
mainto confirm what the option now does and where it stops, and drafted the replacement text; I reviewed and edited it before pushing.Generated by Claude Code