ruvnet/ruflo · error

WASM GNN module not available, using JS fallback

Error message

WASM GNN module not available, using JS fallback

What it means

Fallback path in GnnBridge.initialize(): dynamic import of the WASM GNN module failed, so the bridge sets wasmModule to null and continues with the pure-JavaScript implementation. Correct but slower results.

Source

Thrown at v3/plugins/code-intelligence/src/bridges/gnn-bridge.ts:101

  private readonly embeddingDim: number;

  constructor(embeddingDim = 128) {
    this.embeddingDim = embeddingDim;
  }

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

    try {
      // Dynamic import of WASM module
      this.wasmModule = await this.loadWasmModule();
      this.initialized = true;
    } catch {
      // Fallback to pure JS implementation
      console.warn('WASM GNN module not available, using JS fallback');
      this.wasmModule = null;
      this.initialized = true;
    }
  }

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

  /**
   * Build code graph from files
   */
  async buildCodeGraph(
    files: string[],
    _includeCallGraph: boolean

View on GitHub (pinned to fa13ee4ad6)

Solutions

1. Ensure the WASM GNN artifact is built and its path is correctly resolved so the native module loads.
2. Check the runtime supports WebAssembly and required WASM features (SIMD/threads) if used.
3. If JS fallback is acceptable, no action needed; otherwise fix the module loading error logged at init.

When it happens

Trigger: The GNN WASM binary is missing, fails to instantiate, or the runtime lacks WASM support; bridge transparently falls back to the pure-JS GNN implementation with lower throughput.

Common situations: See trigger scenarios.

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