lib-bpmn-engine is meant to be an embedded engine.
The architectural guidelines focus on core BPMN execution capability.
There is no support for databases or other external IO.
Also, due to Go's compact and powerful syntax, the code base is just a few hundred lines of code
and so very attractive to be transpiled into WASM.
This would enable a broad range of
This is an experiment as well, to learn if there's a need/demand for such a piece of technology.
Admitting, this is kind of an extra playground :)
acceptance criteria
the engine is available as wasm artifact (likely a .JS file)
Github actions are in place, to build wasm artifacts on every release automatically
npm package registry is considered/evaluated to be used as a release hub -- vs. a Github one
an example implementation is available at the GH pages documentation
some marketing is made: e.g. is there some special site, listing "interesting" WASM projects? (like e.g. npm is the number one for JS based projects ... if there's some similar go-to place for WASM, this lib should be listed there)