Control over caching pre-release, stable release or latest #46
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
|
+1 for this. This would be very useful for the project I work on. |
|
Is this going to be merged in? |
safinn
force-pushed
the
stableReleaseIfNewest
branch
from
247d689 to
ca380fe
Compare
|
@safinn is attempting to deploy a commit to the Vercel Team on Vercel. A member of the Team first needs to authorize it. |
safinn
force-pushed
the
stableReleaseIfNewest
branch
from
ca380fe to
93a1112
Compare
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.
Fixes #20
ONLY_PREenvironment variable. When set, the latest pre-release is cached.PREenvironment variable is set, pre-releases are considered to be cached depending on if it is the latest. If not set, only stable releases are cached.lint-stagedto7.2.0to work with Node.JS 10+.testURLin the Jest config due to a JSDom bug described here.