Jaco Greeff
da946b18ce
* Polyfill require adjust
* Assert in promise for getRandomBytes
* Adjust jest
* Revert explicit overrides (from base)
* use typeof
* Re-add crypto-polyfill (backwards, direct imports)
* crypto log
* Fix dev
* Adjust
* Cleanups, no sed mangling
* Cleanup build folder
* Remove exports
* Cleanups
* Adjust env vs util
* Remove Buffer alloc
* Cleant ext vs int
* Rework naming
* Mapping rename
* Combine index & exports
* withWasm wrapper
* pass{String, U8a} -> alloc{String, U8a}
* Internal reuse
* Explict package-only test
@polkadot/wasm
Various WASM wrappers around Rust crates
overview
It is split up into a number of internal packages, namely utilities -
- wasm-crypto Various hashing functions, sr25519 & ed25519 crypto
These are split from the polkadot-js/util repo where it is heavily used as part of @polkadot/util-crypto. (There JS fallbacks are available for some interfaces, e.g. hashing, but for sr25519 WASM is the only interface). Since these don't undergo massive changes on a daily basis and has a build overhead (WASM compilation & optimisation), it is better managed as a seperate repo with a specific CI configuration.
development
Contributions are welcome!
To start off, this repo (along with others in the @polkadot family) uses yarn workspaces to organise the code. As such, after cloning, its dependencies should be installed via yarn, not via npm; the latter will result in broken dependencies.