Add support for loadConfig to resolver plugins #8847
Merged
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.
This adds support for
loadConfig
to resolver plugins. Configs are loaded once per build, and passed to theresolve
function. The default resolver uses this to create an instance of theNodeResolver
once per build so that it can cache things like package.jsons and fs stat calls. This represents a pretty significant performance improvement.We also seemed to be lacking some cache invalidation for dev dependencies in the PathRequest, so now that is added as well along with cache tests.