malice

[package]

name = "malice-worker"

version = "0.1.0"

edition = "2024"

publish = false

# malice-worker's wasm profile needs are workspace-wide settings (debug info off

# for dev, panic=abort and LTO for release) that would otherwise leak into

# malice-server's native build if this crate stayed in the root workspace, so it

# gets its own, like macltok's harness/web.

[workspace]

[lib]

crate-type = ["cdylib", "rlib"]

[target.'cfg(target_family = "wasm")'.dependencies]

macltok = { git = "ssh://brewery@pls.lobotomise.me:33/atagen/macltok", rev = "f137a3c74d1144698237fe4ac1bddd483f9ec85e", features = ["indexeddb", "serde", "mirror"] }

malice-core = { path = "../malice-core" }

ruma = { version = "0.16", default-features = false }

futures-util = { version = "0.3", default-features = false, features = ["std"] }

futures-channel = "0.3"

serde_json = "1"

# pinned exactly so flake.nix's wasmBindgenCli, built for this locked version, matches

# what wasm-bindgen-test-runner needs at test time

wasm-bindgen = "=0.2.128"

wasm-bindgen-futures = "=0.4.78"

js-sys = "=0.3.105"

[dev-dependencies]

wasm-bindgen-test = "0.3"

web-sys = { version = "0.3", features = ["SharedWorkerGlobalScope"] }

gloo-timers = { version = "0.3", features = ["futures"] }

[lints.rust]

unsafe_code = "forbid"

# with debuginfo the test wasm balloons and can OOM the test runner, per macltok's

# own harness/web/Cargo.toml

[profile.dev]

debug = false

[profile.release]

opt-level = "z"

lto = true

codegen-units = 1

panic = "abort"

strip = true