Official standard-library packages for Edge Python. Most are a Rust crate compiled to wasm32-unknown-unknown against the wasm-pdk ABI; hosts load the resulting .wasm over the standard plugin contract, no custom embedder, no Rust on the consumer side. A package can also ship as pure Edge Python source (src/entry.py), imported as a code module with no cargo build (e.g. test).

The folder name IS the package name. A native package builds to <name>/target/wasm32-unknown-unknown/release/<name>.wasm; a pure-Python package has src/entry.py and no build artifact. Each package's <name>.json corpus sits in its folder; cases in it are automatically prefixed with from <name> import *\n before dispatch, so the corpus only contains the code being tested.

Native packages build independently; the agnostic runner asserts against the produced .wasm, or against src/entry.py for a pure-Python package. From the repo root:

# Build a native package's .wasm artifact (skip for pure-Python packages like test).
( cd json && cargo build --release --target wasm32-unknown-unknown )

# One command, drives all corpora through the shared runner.
deno test --allow-all tests/

The runner discovers packages by walking the repo root for <name>/<name>.json corpora. CI runs this matrix via .github/workflows/.

For a native (wasm) package:

1. Create <name>/ at the repo root with Cargo.toml (name = "<name>", crate-type = ["cdylib"], wasm-pdk dep) and a src/lib.rs exporting via #[plugin_fn].
2. Drop <name>/<name>.json with the corpus (Edge Python source + expected output / error per case).
3. Run cargo build --release --target wasm32-unknown-unknown inside the package folder.
4. Run deno test --allow-all tests/ from the repo root.

For a pure-Python package, skip the crate: add <name>/src/entry.py plus <name>/<name>.json, then run deno test --allow-all tests/. The runner routes .py packages to their source and skips the wasm build.

No edits to tests/.

MIT OR Apache-2.0