ruvnet/ruflo · error · Error

Failed to load WASM module: ${moduleName}

Error message

Failed to load WASM module: ${moduleName}

What it means

The WASM loader exhausted every candidate path for the named module without a successful load (all fetches/readFile attempts failed or were caught). The final fallback error names the module; check that the WASM artifact is installed/bundled and reachable on the configured paths.

Source

Thrown at v3/plugins/gastown-bridge/src/wasm/loader.ts:172

                  new DecompressionStream('gzip')
                );
                return new Response(decompressed).arrayBuffer();
              }
            }
            // Fallback: assume server decompresses or use pako
            throw new Error('Gzip decompression not supported');
          }

          return buffer;
        }
      }
    } catch {
      // Try next path
      continue;
    }
  }

  throw new Error(`Failed to load WASM module: ${moduleName}`);
}

/**
 * Instantiate a WASM module
 */
async function instantiateWasm<T>(
  bytes: ArrayBuffer,
  imports: WebAssembly.Imports = {}
): Promise<WasmModule<T>> {
  const module = await WebAssembly.compile(bytes);
  const instance = await WebAssembly.instantiate(module, imports);

  return {
    instance: instance.exports as T,
    memory: instance.exports.memory as WebAssembly.Memory,
    ready: true,
  };
}

View on GitHub (pinned to fa13ee4ad6)

Solutions

1. Check the underlying initialization error; verify the WASM asset exists, is compatible, and required dependencies are loaded.
2. Retry initialization after fixing the root cause; make the failure surface the original error message.

When it happens

Trigger: Thrown at v3/plugins/gastown-bridge/src/wasm/loader.ts:172 when the library encounters an invalid state.

Common situations: See trigger scenarios.

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