The @causl/causl-wasm-ts/wasm subpath was never imported in this
process, so no wasm engine was ever registered. Now a
CAUSL_WASM_ENGINE_UNAVAILABLE throw.
The subpath IS imported but preloadCauslWasm() has not RESOLVED. Now a
CAUSL_WASM_NOT_PRELOADED throw from the subpath's own
CauslWasmNotPreloadedError.
§18A.13.1 — a module IS preloaded but the WasmGC engine cannot
instantiate on this host. Now a CAUSL_WASM_ENGINE_UNAVAILABLE throw;
the capability fallback that used to absorb it is gone.
Since 0.5.0 — createCausl() throws rather than returning a
pure-TypeScript graph, so no value of this type is ever produced. Retained
with CauslCapabilityFallbackEvent so a 0.4.x adopter's listener
still compiles; both are removed in 0.6.0. Branch on the thrown error's
code instead (CAUSL_WASM_ENGINE_UNAVAILABLE /
CAUSL_WASM_NOT_PRELOADED).
— carried on CauslCapabilityFallbackEvent.reason.
WHY an implicit
createCausl()returned a pure-TypeScript graph.