ruvnet/ruflo · error

WASM initialization failed, using JS fallback

Error message

WASM initialization failed, using JS fallback

What it means

Log warning in initializeWasm: constructing/initializing the WASM loader failed, so the gastown plugin sets wasmInitialized=false and all WASM-backed operations run the JavaScript fallback paths.

Source

Thrown at v3/plugins/gastown-bridge/src/index.ts:1031

  }

  private async initializeWasm(): Promise<void> {
    try {
      this.wasmLoader = new WasmLoaderAdapter();

      if (this.config.wasm?.preload) {
        await preloadWasmModules();
      }

      await this.wasmLoader.initialize();
      this.wasmInitialized = this.wasmLoader.isInitialized();

      if (this.wasmInitialized) {
        const versions = await getWasmVersions();
        this.logger.info('WASM modules initialized', { versions });
      }
    } catch (error) {
      this.logger.warn('WASM initialization failed, using JS fallback', {
        error: error instanceof Error ? error.message : String(error),
      });
      this.wasmInitialized = false;
    }
  }

  private async checkCliAvailable(): Promise<boolean> {
    try {
      const { exec } = await import('child_process');
      const { promisify } = await import('util');
      const execAsync = promisify(exec);

      await execAsync('which gt');
      await execAsync('which bd');
      return true;
    } catch {
      return false;
    }

View on GitHub (pinned to fa13ee4ad6)

Solutions

1. Check the WASM initialization error; the JS fallback keeps functionality — rebuild or reinstall the WASM artifacts to restore performance.

When it happens

Trigger: Thrown at v3/plugins/gastown-bridge/src/index.ts:1031 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/2271db7519925303. Report an issue: GitHub.