Audited & minimal JS implementation of hash functions, MACs and KDFs.
I've spotted this after benchmarks were transitioned from common.js to ESM in 88c1aa30674348f497f936e497d734a15f53be26. Check out `main` branch. - `git clone [email protected]:paulmillr/noble-hashes.git && cd noble-hashes && npm install && npm run build && npm run bench:install` - Comment-out lines 14-28 in benchmark/hashes.js, run again. sha3 would become 25% faster We need to investigate: 1. Why sha3 is 25% slower when other modules are imported 2. Why sha2 is NOT slower when other modules are imported. What's special about sha3? 3. Why everything was fine with common.js, but is slow with ESM? 4. *Bonus issue:* re-exporting `isBytes` slows-down performance considerably. See branch https://github.com/paulmillr/noble-hashes/tree/import-perf. Probably related. To investigate this, v8/node.js profiling, memory dumps, etc may help.
This issue appears to be discussing a feature request or bug report related to the repository. Based on the content, it seems to be resolved. The issue was opened by paulmillr and has received 0 comments.