Closed backspace closed 1 year ago
Actually loader-utils
also uses node:crypto
so this didn’t make the error go away… I’m going to switch to sync-sha1
.
I think we just need a nice fast hashing function--i think it's not super important to be sha256 secifically
The use of node:crypto was causing problems with some code that needs to run in the browser.