Deploy Wasm in CI #156

Closed
opened 2026-07-07 23:17:10 +00:00 by Quaternions · 1 comment

The wasm is currently committed in tree. There are many downsides to this. Remove it from the source control and have the build step deploy the executable code directly.

The wasm is currently committed in tree. There are many downsides to this. Remove it from the source control and have the build step deploy the executable code directly.
Owner

Shipped in v0.43.2 (PR #168): web/pkg is out of the repo and the wasm is now built inside the Docker pipeline (wasm-bindgen 0.2.120 / wasm-pack 0.14.0 / binaryen 130) plus in web-e2e before Playwright. First docker-build with the new stage went green and the freshly CI-built wasm is what's serving on /play now.

Shipped in v0.43.2 (PR #168): web/pkg is out of the repo and the wasm is now built inside the Docker pipeline (wasm-bindgen 0.2.120 / wasm-pack 0.14.0 / binaryen 130) plus in web-e2e before Playwright. First docker-build with the new stage went green and the freshly CI-built wasm is what's serving on /play now.
Sign in to join this conversation.
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: funman300/Ferrous-Solitaire#156