-
Notifications
You must be signed in to change notification settings - Fork 775
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bump @chainsafe/ssz
to 0.11.0
#2622
Conversation
Codecov Report
Additional details and impacted files
Flags with carried forward coverage won't be shown. Click here to find out more. |
Hmm, looks like the |
I think I've resolved the karma import issue. Will approve if CI passes |
There could be an argument that this should be solved in the SSZ package itself. Since other tools may struggle with the exports configuration too. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks a lot, cool 🙂, will approve and merge!
Congrats, your important contribution to this open-source project has earned you a GitPOAP! GitPOAP: 2023 EthereumJS Contributor: Head to gitpoap.io & connect your GitHub account to mint! Learn more about GitPOAPs here. |
If you solve this in the SSZ package let us know, then we likely also want to do another update on this. We have releases planned for roughly in 10 days or so, if this will happen it would be great if we could already take the updated version in. |
8.0.4 introduces WASM-dependent ssz. Once a version of @ethereumjs/util has been released which does not transitively depend on WASM-dependent as-sha256, this can be lifted. Context: ethereumjs/ethereumjs-monorepo#2622
8.0.4 introduces WASM-dependent ssz. Once a version of @ethereumjs/util has been released which does not transitively depend on WASM-dependent as-sha256, this can be lifted. Context: ethereumjs/ethereumjs-monorepo#2622
Bumps
@chainsafe/ssz
to0.11.0
.The current version of
@chainsafe/ssz
uses an AssemblyScript based SHA-256 implementation that causes issues on some platforms since it requiresWebAssembly
for execution (e.g. in sites or extensions with strict CSPs).This new version uses a pure JS implementation (
@noble/hashes
) as the default hasher for SHA-256 and should fix some of these aforementioned incompatibility issues.For more context see: ChainSafe/ssz#313