Browser object writer
Browser companions omit the direct-WASM object writer and its instruction and declaration recording support by default. Ordinary direct-WASM applications do not need this support. Native compiler tools continue to include it.
To include the writer in a browser companion, add direct-wasm-writer to the application's build configuration in package.sgl:
(config
name: 'web
backend: 'direct-wasm
toolchain: 'zig
target: "wasm32-wasi"
features: '(web wasm direct-wasm-writer))The final application selects the feature. The builder recompiles the runtime with SIGIL_DIRECT_WASM_WRITER=1 and explicitly links the object writer and emission adapter. It exports direct_wasm_object_link and the adapter's create, destroy and sink_v2 C entry points. C consumers can reference the remaining adapter APIs directly. The existing object format, validation and ownership requirements still apply; enabling the writer does not select it as the application's compilation backend.
Without the feature, explicit body-sink compilation requests fail with direct-WASM writer is disabled. Ordinary byte and WASM emission remain available. For a manually built browser runtime, compile all runtime objects consistently with -DSIGIL_DIRECT_WASM_WRITER=1 to enable writer support.
The feature participates in runtime archive and companion cache identities. Switching it off again selects a runtime without the writer.