Downstream distribution of wasm-bindgen and wasm-pack binaries

[kpcyrd]

💡 Feature description

Hello! I'm involved with distributing wasm-pack and wasm-bindgen binaries in Alpine. This is currently quite involved, since they tightly coupled even though they are shipped as two independent programs:

• https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/107987
• https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/104889
• https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/103048
• https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/101784
• https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/98705

See also this discussion:

https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/102938#note_614588

💻 Basic example

It would be much easier if, for example, wasm-bindgen and wasm-pack could be built from the same source code release, ensuring they are always compatible with each other.

What do you think? :)

[guybedford]

Funnily enough we were just discussing moving wasm-pack into the wasm-bindgen monorepo and got approval from the team to start investigating this, and one of the areas that comes up with this is how to manage the separate release processes.

All this to say, we expect the future process now to be a clone of the wasm-bindgen repo, and then two separate binaries built from there.

I can keep this thread updated with progress on that effort.