Cache parsed tsConfig and webpackConfig files to speed up lookups
#110
Conversation
This file contains 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
AMoo-Miki
added a commit
to AMoo-Miki/node-dependency-tree
that referenced
this pull request
Jan 31, 2023
Signed-off-by: Miki <[email protected]>
AMoo-Miki
force-pushed
the
cache-parsed-config
branch
from
64e0134 to
f476891
Compare
|
This needs a rebase, and tests |
|
Feel free to make a new PR and CC me. |
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.
A map is created to store parsed
tsConfigcompiler options and resolvedwebpackConfig. Before parsing each, the cache is checked and used if anything is found there.Fixes #96
Signed-off-by: Miki [email protected]