We currently have to copy or symlink the wasm artifact in bb and circuits from src to dest after every build. This also needs to be manually done by every package that depends on either of those in the Dockerfile CI, which is error prone.
If we moved the wasm artifact to a different folder, we could remove the need for doing this. Keep in mind such a folder needs to be included when npm publishing.
Alternatively, we can set up individual packages that only have the wasm and have no build process, and import from them, but this goes against #96.
We currently have to copy or symlink the wasm artifact in bb and circuits from
srctodestafter every build. This also needs to be manually done by every package that depends on either of those in the Dockerfile CI, which is error prone.If we moved the wasm artifact to a different folder, we could remove the need for doing this. Keep in mind such a folder needs to be included when
npm publishing.Alternatively, we can set up individual packages that only have the wasm and have no build process, and import from them, but this goes against #96.