merman-typst-plugin 0.8.0-alpha.3

Typst WebAssembly plugin bridge for merman SVG rendering.
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74

# merman-typst-plugin

`merman-typst-plugin` is the experimental Typst WebAssembly plugin bridge for
`merman`.

The crate exports Typst-compatible `wasm-minimal-protocol` functions and delegates
rendering and validation to `merman-bindings-core`.

Current exported functions:

- `abi_version() -> bytes`
- `package_version() -> bytes`
- `capabilities_json() -> bytes`
- `render_svg_json(source: bytes, options_json: bytes) -> bytes`
- `validate_json(source: bytes, options_json: bytes) -> bytes`

`render_svg_json` returns a stable JSON payload with `ok`, `code`,
`code_name`, `message`, and `svg` fields so the Typst package can render
placeholder or text errors without failing compilation.

## ABI Boundary

Current Typst plugin ABI version: `1`.

The plugin ABI covers the exported `wasm-minimal-protocol` function names and
their byte payload contracts. That includes the `abi_version`,
`package_version`, `capabilities_json`, `render_svg_json`, and `validate_json`
exports, plus the JSON schemas consumed or produced by those exports.

Typst wrapper API changes in `packages/typst/merman/src/*.typ` do not require a
plugin ABI bump when this WebAssembly surface remains stable. Bump
`TYPST_PLUGIN_ABI_VERSION` and update the ABI tests and package README mapping
when an export is added, removed, renamed, changes argument or return bytes, or
changes the render, validate, or capabilities JSON contract.

The `package_version` export reports the Rust crate version. The Typst package
version in `packages/typst/merman/typst.toml` is a separate `@preview` wrapper
version.

Build the default Typst render artifact with:

```bash
cargo build -p merman-typst-plugin --profile wasm-size --target wasm32-unknown-unknown
```

Build the bridge-only protocol artifact with:

```bash
cargo build -p merman-typst-plugin --profile wasm-size --target wasm32-unknown-unknown --no-default-features
```

Build a pure render artifact without validation analysis with:

```bash
cargo build -p merman-typst-plugin --profile wasm-size --target wasm32-unknown-unknown --no-default-features --features render
```

Build the larger full-config/full-sanitization no-host artifact with:

```bash
cargo build -p merman-typst-plugin --profile wasm-size --target wasm32-unknown-unknown --features core-full
```

Then check the Typst wasm surface with:

```bash
cargo run -p xtask -- profile-budget check-wasm --profile typst-wasm --wasm target/wasm32-unknown-unknown/wasm-size/merman_typst_plugin.wasm
```

Smoke the plugin through a Typst-compatible `wasmi` host call with:

```bash
cargo run -p xtask -- typst-plugin-smoke --wasm target/wasm32-unknown-unknown/wasm-size/merman_typst_plugin.wasm
```