std/_wasm_crypto
2022-02-02 23:21:39 +09:00
..
.cargo crypto(build): update Rust and Rust dependencies (#1805) 2022-01-09 15:49:02 +01:00
src feat(crypto): add md4 hash (#1799) 2022-01-09 17:32:54 +01:00
_build.ts chore: update copyright header (#1871) 2022-02-02 23:21:39 +09:00
.rustfmt.toml feat(crypto): add std/crypto wrapping and extending runtime WebCrypto (#1025) 2021-07-29 04:37:02 -07:00
Cargo.lock feat(crypto): add md4 hash (#1799) 2022-01-09 17:32:54 +01:00
Cargo.toml feat(crypto): add md4 hash (#1799) 2022-01-09 17:32:54 +01:00
crypto.js crypto(build): update Rust and Rust dependencies (#1805) 2022-01-09 15:49:02 +01:00
crypto.wasm.js feat(crypto): add md4 hash (#1799) 2022-01-09 17:32:54 +01:00
mod.ts chore: update copyright header (#1871) 2022-02-02 23:21:39 +09:00
README.md chore: add instruction for updating _wasm_crypto artifacts (#1807) 2022-01-10 16:14:59 +01:00
rust-toolchain.toml crypto(build): update Rust and Rust dependencies (#1805) 2022-01-09 15:49:02 +01:00
test.ts chore: update copyright header (#1871) 2022-02-02 23:21:39 +09:00

std/_crypto_wasm is only for internal use, such as by std/crypto and std/node/crypto. Its interface may not be stable between releases and it should not be imported directly.

How to Build

Prerequisite

Requires the wasm-bindgen CLI.

# This must match the version of wasm-bindgen in Cargo.lock:
cargo install -f wasm-bindgen-cli --version 0.2.78

Build

deno run --allow-all ./_build.ts

This will regenerate ./crypto.js and ./crypto.wasm.js from the Rust source.

CI

If CI fails in Verify WASM hasn't changed step, you need to download built artifacts from that CI run and commit them back to the PR. Visit https://github.com/denoland/deno_std/actions/runs/<CI_RUN_ID>#artifacts and click on Artifacts at the top of the page.