An old issue with SVGBob leaking styles in wasm builds (where the SVG is placed alongside other content) has uncovered an inconvenient situation in the community maintenance with wasm npm builds of svgbob. This issue has been fixed since 7.0, but community wasm builds have not kept up with updates, making downstream packages stuck with an unpleasant experience.
I made what felt like the smallest wrapper I could make as an example, but we'd have the same issue with community builds needing to update in sync with official svgbob updates. Is there any room for an official svgbob wasm build to be maintained?
Love SVGBob!
An old issue with SVGBob leaking styles in wasm builds (where the SVG is placed alongside other content) has uncovered an inconvenient situation in the community maintenance with wasm npm builds of svgbob. This issue has been fixed since 7.0, but community wasm builds have not kept up with updates, making downstream packages stuck with an unpleasant experience.
I made what felt like the smallest wrapper I could make as an example, but we'd have the same issue with community builds needing to update in sync with official svgbob updates. Is there any room for an official svgbob wasm build to be maintained?