Skip to content

Latest commit

 

History

History
72 lines (44 loc) · 2 KB

File metadata and controls

72 lines (44 loc) · 2 KB
title Questions
section AngleSharp.Wasm

Frequently Asked Questions

For a compact section-by-section status view, see Spec Coverage Matrix.

Which .NET versions are supported?

AngleSharp.Wasm currently targets .NET 8 and .NET 10.

Is the full WebAssembly JS API specification implemented?

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

Is window.WebAssembly available?

Yes, when used with a scripting integration that discovers DOM-annotated members from registered assemblies.

Are APIs synchronous or asynchronous?

The current bridge methods are synchronous from the caller perspective.

Are Memory, Table, Global, and Tag exposed as full JS API objects?

Not yet. Non-function exports currently appear as WasmJsExportValue descriptors (name, kind).

How do I invoke exported functions?

Either call:

  • instance.Invoke("exportName", args...)

or use the export wrapper:

  • ((WasmJsExportedFunction)instance.Exports["exportName"]).Invoke(args...)

What does Module.customSections(name) return?

It returns all matching custom section payloads as byte[][].

How are host imports provided?

Use WithWasmImports(...) with either:

  • an IWasmImportProvider, or
  • a delegate returning IEnumerable<WasmImportFunction>.

Which value kinds are currently supported for invocation/import marshaling?

Current numeric value kinds are supported:

  • i32
  • i64
  • f32
  • f64

What are known limitations today?

  • No Promise-based compile / instantiate bridge 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.