Currently in order to build compatible cap9 WASM binaries we use a combination of things including wasm-build and a custom pre-processor. We should move all this functionality into cap9-cli including the parts of wasm-build. While it would be good for wasm-build to be separate, due to the way it handles file paths it would be simpler to replicate it's functionality.
Currently in order to build compatible cap9 WASM binaries we use a combination of things including
wasm-build
and a custom pre-processor. We should move all this functionality intocap9-cli
including the parts ofwasm-build
. While it would be good forwasm-build
to be separate, due to the way it handles file paths it would be simpler to replicate it's functionality.