fix(config): upgrade md4 -> md5 on node > 16 #19108
Merged
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.
π Linked issue
resolves #10844
#19078
β Type of change
π Description
We have a tricky situation upcoming, with Node 16 due to be EOL on September 11th, 2023, but Nuxt 2 is not EOL until the end of the year.
Webpack 4 hard-codes
md4
algorithm in several places in the code base meaning our options to resolve this for Nuxt 2 users are somewhat limited. In build/dev mode, this change monkey patches thecrypto.createHash
function if running on Node > 16 to upgrademd4
tomd5
. Would welcome other ideas too ππ Checklist