[rush-resolver-cache] Cache nested package info#5321
Merged
dmichon-msft merged 1 commit intomicrosoft:mainfrom Aug 26, 2025
Merged
[rush-resolver-cache] Cache nested package info#5321dmichon-msft merged 1 commit intomicrosoft:mainfrom
dmichon-msft merged 1 commit intomicrosoft:mainfrom
Conversation
iclanton
approved these changes
Aug 26, 2025
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.
Summary
Improves the performance of
@rushstack/rush-resolver-cache-pluginby caching information about nested package.json files in packages across installs based on package integrity hashes.Details
Persists an additional file into common/temp that stores the results of the scan for each package integrity hash.
How it was tested
Local runs on a repository using this plugin. Reduced time spent in the rush-resolver-cache plugin from 2647ms to 443ms (most of which is loading the shrinkwrap file).
This could be further reduced if the
afterInstallhook was passed the shrinkwrap file used for installation, skipped if no install occurred, or at least passed an indicator if an install occurred.Impacted documentation
None.