ruvnet/ruflo · error
WASM MinCut module not available, using JS fallback
Error message
WASM MinCut module not available, using JS fallback
What it means
Fallback path in MinCutBridge.initialize(): the WASM min-cut module could not be loaded, so the bridge runs its pure-JS implementation instead. All downstream methods (findOptimalCuts, minSTCut, etc.) work but with reduced performance.
Source
Thrown at v3/plugins/code-intelligence/src/bridges/mincut-bridge.ts:86
*/
export class MinCutBridge implements IMinCutBridge {
// WASM module for future performance optimization (currently uses JS fallback)
private wasmModule: MinCutWasmModule | null = null;
private initialized = false;
/**
* 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 MinCut module not available, using JS fallback');
this.wasmModule = null;
this.initialized = true;
}
}
/**
* Check if initialized
*/
isInitialized(): boolean {
return this.initialized;
}
/**
* Find optimal module boundaries using MinCut
*/
async findOptimalCuts(
graph: DependencyGraph,
numModules: number,View on GitHub (pinned to fa13ee4ad6)
Solutions
- Build/ship the WASM MinCut module and verify its load path so the native implementation is used.
- Check WebAssembly support and required feature flags in the runtime.
- If the JS fallback is intended, no action needed; it is slower but functionally equivalent.
Defensive patterns
Strategy: fallback
When it happens
Trigger: The MinCut WASM module cannot be loaded or instantiated (missing artifact, unsupported runtime); bridge falls back to the JS MinCut implementation.
Common situations: See trigger scenarios.
AI-assisted analysis of ruvnet/ruflo@fa13ee4ad6 (2026-08-18).
Data as JSON: /api/errors/3a5262f3e8ad10ab.
Report an issue: GitHub.