Use md5 hash for caching on node v17#918
Merged
nicolo-ribaudo merged 3 commits intobabel:mainfrom Oct 20, 2021
Merged
Conversation
Contributor
Author
Member
|
Would it be a breaking change to just switch to md5 by default? |
Contributor
Changing hash algorithm will invalidate current cache. I think offering a |
Contributor
Author
|
@JLHwung I switched the change to conditionally switch to md5 if it detects node v17.0.0 or higher. |
md5 has for caching on node v17
md5 has for caching on node v17md5 hash for caching on node v17
1 task
1 task
This was referenced May 19, 2024
This was referenced May 26, 2024
This was referenced Sep 14, 2024
This was referenced Sep 20, 2024
This was referenced Sep 27, 2024
This was referenced Oct 1, 2024
1 task
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.
Please check if the PR fulfills these requirements
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
What is the current behavior? (You can also link to an open issue here)
#917
What is the new behavior?
Webpack builds will succeed with latest node version 17.0.0 if you set the new "hashType" configuration value to "md5".
Does this PR introduce a breaking change?