Announcing Backward Compatibility for Wasm plugins

We are thrilled to announce a major quality-of-life improvement for the entire SWC ecosystem. Starting from @swc/core v1.15.0, our Wasm plugins are now backward-compatible!

Previously, developers using Wasm plugins often had to update them with each new release of @swc/core to ensure compatibility. This created friction, added maintenance overhead, and could disrupt development workflows.

Thanks to the introduction of a stable Application Binary Interface (ABI), this is no longer the case. A Wasm plugin compiled against v1.15.0 will now work seamlessly with future versions of SWC. This change dramatically improves stability and reduces the maintenance burden for both plugin authors and end-users.

This significant achievement was made possible by the incredible work on PR #11198. We want to extend our heartfelt gratitude to quininer on Github and the rspack team for their pivotal contributions and dedication.

This enhancement will directly improve the developer experience for everyone using the SWC project, as well as for users of downstream projects such as rspack and next.js.

Upgrade to v1.15.0 today and enjoy a more stable and seamless plugin experience!

Note: Still, some changes are not backward-compatible, but it’s now much easier to avoid a breaking chnage and we will.