-
Notifications
You must be signed in to change notification settings - Fork 71
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
refactor(cache): simplify creating / using the cache
var
#415
Merged
ezolenko
merged 1 commit into
ezolenko:master
from
agilgur5:refactor-cache-simplify-create
Aug 30, 2022
Merged
refactor(cache): simplify creating / using the cache
var
#415
ezolenko
merged 1 commit into
ezolenko:master
from
agilgur5:refactor-cache-simplify-create
Aug 30, 2022
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
agilgur5
added
kind: bug
Something isn't working properly
kind: internal
Changes only affect the internals, and _not_ the public API or external-facing docs
scope: cache
Related to the cache
scope: watch mode
Related to Rollup's watch mode
labels
Aug 25, 2022
- as everything is created in the `buildStart` hook now (which has `RollupContext`), we can create the `cache` there too - no need for slightly hacky, lazy creation during `transform` anymore - simplifies it and also standardizes it so it's created the same way as all the other instance vars - fix: reset `cache` after each watch cycle - previously the cache was never reset, meaning that if anything became dirty in a watch cycle, it would never get reset back - in some cases, this would mean that the cache was effectively always dirty during an entire watch mode run, and therefore never used - this would be quite inefficient as the FS usage for the cache would just go to waste - see that test coverage has now increased as a result!
agilgur5
force-pushed
the
refactor-cache-simplify-create
branch
from
August 29, 2022 22:07
2fcae7c
to
0dabda3
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
kind: bug
Something isn't working properly
kind: internal
Changes only affect the internals, and _not_ the public API or external-facing docs
scope: cache
Related to the cache
scope: watch mode
Related to Rollup's watch mode
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.
NOTE: this is built on top of #414 as it uses thebuildStart
changes made there. As such, I've marked this PR as "Draft" until #414 is merged.Rebased on top and marked as ready for review.
Summary
Use the
buildStart
hook added in #414 to simplifycache()
tocache
Details
as everything is created in the
buildStart
hook now (which hasRollupContext
), we can create thecache
there tootransform
anymorefix: reset
cache
after each watch cycle