feat: document swc wasm plugin compatibility with Rspack - #360
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
DakEnviy
approved these changes
Sep 14, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds a note to the
swcconfig option in the README: custom wasm plugins passed throughjsc.experimental.pluginsmust match theswc_coreABI of the bundler running the build, which forbundler: 'rspack'is theswc_coreembedded in Rspack rather than the@swc/coreversion.Why
This came up while upgrading Rspack to 2.2.1 (#359). Rspack 2.2.x embeds
swc_core77, which forces@swc/coreto1.16.0–1.16.1and@swc/plugin-transform-importsto exactly13.0.0. A mismatched wasm plugin does not warn — it fails to load at build time, and the coupling was not documented anywhere.It also carries a
featcommit so the Rspack 2.2.1 upgrade in #359 gets released: that PR was renamed tofeatonly after it had already been squashed, so it landed onmainaschore(deps): ...and release-please will not cut a release for it on its own.Reviewer notes
Docs only — no code, no dependency changes.
🤖 Generated with Claude Code