ruvnet/ruflo · error · Error

Gzip decompression not supported

Error message

Gzip decompression not supported

What it means

The WASM loader fetched a .gz artifact in a browser/edge context where no gzip decompression path exists — neither DecompressionStream nor a bundled inflater is available. Rather than serving garbage bytes, the loader throws; use an uncompressed module or a decompression-capable environment.

Source

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

      } else {
        // Browser/Edge: Use fetch
        const response = await customFetch(path, { signal });
        if (response.ok) {
          const buffer = await response.arrayBuffer();

          if (path.endsWith('.gz')) {
            // Decompress in browser using DecompressionStream if available
            if (typeof DecompressionStream !== 'undefined') {
              const stream = new Response(buffer).body;
              if (stream) {
                const decompressed = stream.pipeThrough(
                  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>(

View on GitHub (pinned to fa13ee4ad6)

Solutions

1. Provide uncompressed WASM, or enable a decompression path (e.g. DecompressionStream or pako) for this environment.

When it happens

Trigger: Thrown at v3/plugins/gastown-bridge/src/wasm/loader.ts:160 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/d3810df8edf0bd29. Report an issue: GitHub.