plugins/wasm/znippy-plugin-maven-wasm/Cargo.toml
[package]
name = "znippy-plugin-maven-wasm"
version = "0.1.0"
edition = "2024"
description = "The WASM example plugin for znippy: the maven handler compiled to wasm32, reusing znippy-plugin-maven"
license = "MIT"
repository = "https://git.gunnar.rs/nordisk/znippy"
authors = ["Rickard Lundin <rickard@ignalina.dk>"]
# Not on crates.io. This is the worked EXAMPLE of the wasm plugin ABI, built to a
# .wasm and loaded by `znippy_common::plugins::wasm_loader::WasmPlugin`; publishing
# it would put a second maven package name on the registry for no consumer.
publish = false
[lib]
# cdylib ONLY: on wasm32-unknown-unknown this is what produces the `.wasm`
# module (with the `memory` export `wasm_loader` reads). There is no rlib
# because nothing links this crate — the loader loads its bytes.
crate-type = ["cdylib"]
[dependencies]
# THE reuse edge. Default features on purpose: that leaves out `host-decompressors`
# (ljar + znippy-zoomies + znippy-common — threads and arrow, neither of which
# crosses to wasm32) and `resolve` (ureq, a network fetch). What is left —
# `pom.rs`, the linflate JAR scan in `lib.rs`, and the shared field writer in
# `row.rs` — is target-independent and compiles unchanged for wasm32.
znippy-plugin-maven = { version = "0.10.0", path = "../../native/znippy-plugin-maven" }
[dev-dependencies]
# Host-side only: the agreement test loads the built .wasm through the real
# loader and compares it against the real native plugin. Neither is built for
# wasm32 — `cargo build --target wasm32-unknown-unknown` never touches dev-deps.
znippy-common = { version = "0.10.0", path = "../../../znippy-common", features = ["wasm-plugins", "host-decompressors"] }
znippy-plugin-maven = { version = "0.10.0", path = "../../native/znippy-plugin-maven", features = ["host-decompressors"] }
znippy-zip-fixtures = { path = "../../../znippy-zip-fixtures" }