Select which wasm variant backs the API (PLAN-166 / PLAN-174): "full"
(default here — everything, including the info meta layer),
"browser-full" (the same conversion capabilities, without the meta
strings) or "bitmark-json" (bitmark ↔ JSON only; markup formats, mapping
report and the lex output unavailable). May be called again to switch — the swap is
atomic between calls and the surface stays valid throughout. On Node loading
is synchronous; the Promise is for API symmetry with the browser entry.
Node defaults to "full" because it loads wasm from disk: only the browser
pays a download-latency cost for richness. Bundling this entry for the
browser is legitimate — select "browser-full" explicitly when you do.
Select which wasm variant backs the API (PLAN-166 / PLAN-174):
"full"(default here — everything, including theinfometa layer),"browser-full"(the same conversion capabilities, without the meta strings) or"bitmark-json"(bitmark ↔ JSON only; markup formats, mapping report and thelexoutput unavailable). May be called again to switch — the swap is atomic between calls and the surface stays valid throughout. On Node loading is synchronous; the Promise is for API symmetry with the browser entry.Node defaults to
"full"because it loads wasm from disk: only the browser pays a download-latency cost for richness. Bundling this entry for the browser is legitimate — select"browser-full"explicitly when you do.