| title | Questions |
|---|---|
| section | AngleSharp.Wasm |
For a compact section-by-section status view, see Spec Coverage Matrix.
AngleSharp.Wasm currently targets .NET 8 and .NET 10.
Not yet. The current implementation covers a useful subset with emphasis on:
- Compiling and instantiating modules
- Reading module metadata (
exports,imports,customSections) - Invoking exported functions
- Registering host imports
Yes, when used with a scripting integration that discovers DOM-annotated members from registered assemblies.
The current bridge methods are synchronous from the caller perspective.
Not yet. Non-function exports currently appear as WasmJsExportValue descriptors (name, kind).
Either call:
instance.Invoke("exportName", args...)
or use the export wrapper:
((WasmJsExportedFunction)instance.Exports["exportName"]).Invoke(args...)
It returns all matching custom section payloads as byte[][].
Use WithWasmImports(...) with either:
- an
IWasmImportProvider, or - a delegate returning
IEnumerable<WasmImportFunction>.
Current numeric value kinds are supported:
i32i64f32f64
- No Promise-based
compile/instantiatebridge methods. - No
validate(...)method yet. - No streaming APIs.
- No compile options support (
builtins,importedStringConstants). - Non-function exports are descriptors instead of full JS API objects.
These limits are expected at this stage and can be expanded in future versions.