Build failure in Angular when using @gorules/zen-engine: Missing '@gorules/zen-engine-wasm32-wasi' dependency

[victor-arredondo-softseti]

IssueGoRulesEngine_gorules-zen-engine-wasm32-wasi.pdf

[ivanmiletic]

Hi @victor-arredondo-softseti we support WASM.

Our newest BRMS simulator runs directly in browser using WASM - our BRMS is built in React and it requires some configuration for packages / vite. However we are not sure if there any additional config needed for WASM in Angular.

From UI frameworks we fully support:

• iOS Swift (3 architectures)
• Android Kotlin (4 architectures)
• Browser via WASM

[victor-arredondo-softseti]

Hi team. Thanks for the quick reply. I still need more technical clarity because the issue remains fully blocking on Angular and appears to be related to the WASM/WASI build configuration of the engine.

Additional technical questions (high-priority)

Is @gorules/zen-engine-wasm32-wasi actually intended for browser environments?
Browsers do not support WASI syscalls (wasi_snapshot_preview1). That module also does not exist on npm and cannot be resolved during Angular (Webpack 5) compilation.

What is the exact WASM module that your React/Vite BRMS uses?

Is it a different build of the engine (not WASI-targeted)?

If so, what package or artifact are you using internally?

Can you provide a browser-targeted WASM build (WASM + ES module loader) compatible with Webpack 5?
Angular requires:

.wasm flagged as webassembly/async

No WASI imports

No filesystem or unsupported syscalls

Is there an official documented process for integrating Zen Engine WASM in non-Vite frameworks (Angular, Vue with Webpack, Next.js Webpack, etc.)?
Your documentation only covers Node.js and Vite.

Can the WASM import in browser.js be made optional or dynamically loaded?
Right now the build fails before runtime because the import is hard-coded:

import wasm from '@gorules/zen-engine-wasm32-wasi';

If there is an alternative browser WASM file, can the loader be swapped or overridden?

Roadmap question:
Are you planning to officially support Angular/Webpack builds? If so, is there a target date or version for a browser-ready WASM distribution?

Why this is critical for our use case

We need identical rule evaluation across:

Angular (offline mode)

Laravel API

Node/Express API

We cannot downgrade because v12 lacks DSL features currently used in production.

Right now the missing WASM module blocks the entire build pipeline.

If helpful:

I can provide a minimal Angular 13 reproduction project showing the exact failure.

Thanks in advance — looking forward to the technical details on the WASM builds.