ruvnet/ruflo · error

WASM DAG module not available, using JS fallback

Error message

WASM DAG module not available, using JS fallback

What it means

Fallback in DAGBridge.initialize(): the WASM DAG module could not be loaded, so all graph operations (critical path, topo sort, cycle detection, float calculation) run on the JavaScript implementation.

Source

Thrown at v3/plugins/legal-contracts/src/bridges/dag-bridge.ts:86

export class DAGBridge implements IDAGBridge {
  // WASM module for future performance optimization (currently uses JS fallback)
  private wasmModule: DAGWasmModule | null = null;
  private initialized = false;

  /**
   * Initialize the WASM module
   */
  async initialize(): Promise<void> {
    if (this.initialized) return;

    try {
      // Dynamic import of WASM module
      // In production, this would load from @claude-flow/ruvector-upstream
      this.wasmModule = await this.loadWasmModule();
      this.initialized = true;
    } catch {
      // Fallback to pure JS implementation if WASM not available
      console.warn('WASM DAG module not available, using JS fallback');
      this.wasmModule = null;
      this.initialized = true;
    }
  }

  /**
   * Check if initialized
   */
  isInitialized(): boolean {
    return this.initialized;
  }

  /**
   * Build obligation dependency graph
   */
  async buildDependencyGraph(
    obligations: Obligation[]
  ): Promise<ObligationTrackingResult['graph']> {

View on GitHub (pinned to fa13ee4ad6)

Solutions

1. Build and ship the WASM DAG module and verify its load path.
2. Check WebAssembly support in the runtime environment.
3. If JS fallback is acceptable, no action needed; note it is slower for large graphs.

When it happens

Trigger: DAG WASM module unavailable; bridge falls back to the JS DAG implementation for obligation graph operations.

Common situations: See trigger scenarios.

AI-assisted analysis of ruvnet/ruflo@fa13ee4ad6 (2026-08-18). Data as JSON: /api/errors/0c3eefaa40bd8212. Report an issue: GitHub.