New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wasm plugins are not backward compatible #5060
Comments
This was referenced Jul 6, 2022
feat(swc/plugin_macro): export new interface for getting plugin schema version (#5060: Part 5)
#5158
Closed
kdy1
changed the title
Versioned struct for the plugin-host serialization
Wasm plugins are not backward compatible
Jan 24, 2024
9 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the feature
This is by far the biggest blocker for the official release for the plugin feature. (I thought I filed this already somehow).
The main issue in here is reducing chances of breaking changes for the plugin. There are 3 possible cases which causes diverge between plugins to the host for serialization / deserialization, namely
Each time this happens, the plugin will not be able to run on the newer versions of swc include those changes. These kind of breaking change itself is unavoidable unfortunately, but also we may be able to reduce the chances of it or at least avoid it happening unexpectedly.
We'll attempt to follow
versioned
struct approach suggested by underlying serialization mechanism (https://github.com/rkyv/rkyv/blob/master/examples/backwards_compat/src/main.rs) with compiler flags. When we need a possible breaking changes it'll be guarded by flags, providing backward compatibility as much as it can. Still worth mentioning this only applies toadding
part - removing, or renaming is a clear breaking change we can't avoid to request plugin bumps up with the latest changes. At least, we hope those kind of operation won't happen that frequently.Babel plugin or link to the feature description
No response
Additional context
#3540
The text was updated successfully, but these errors were encountered: