browserify / browserify/createHash
[Breaking] Node v17 crypto removed ripemd160
Open
- Dominant language
- JavaScript
- Stars
- 53
- Forks
- 37
- PR merge metrics
- No merged PRs in 30d
Description
Related: https://github.com/bitcoinjs/bip32/issues/59
Seems like the only option is:
1. Check if version >= 17
2. If true, the index.js should also try to intercept ripemd160 calls and use pure JS.
Thoughts?
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with index.js and the related bitcoinjs/bip32 issue to understand how ripemd160 is currently handled and what changed in Node v17. Verify the failure under Node v17, then determine the compatibility behavior required for ripemd160 and confirm it with the project's existing checks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- cryptography
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100