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
Plugin execution fails if plugin binary enables LTO #7479
Comments
This allows the swc-plugin to work with Next.js v13.4.10, or later, as documented on https://swc.rs/docs/plugin/selecting-swc-core. As part of upgrading, we also set `lto = false` because of build failures that have been popped up (swc-project/swc#7479). Closes: dotansimha#9450
Thanks @kwonoj for referring me here. Based on my experience, it seems like we do have a clue now. |
This allows the swc-plugin to work with Next.js v13.4.10, or later, as documented on https://swc.rs/docs/plugin/selecting-swc-core. As part of upgrading, we also set `lto = false` because of build failures that have been popped up (swc-project/swc#7479). Closes: dotansimha#9450
Disable LTO on release build. refs swc-project/swc#7479
This allows the swc-plugin to work with Next.js v13.4.10, or later, as documented on https://swc.rs/docs/plugin/selecting-swc-core. As part of upgrading, we also set `lto = false` because of build failures that have been popped up (swc-project/swc#7479). Closes: dotansimha#9450
I think this issue can be closed as we updated |
Note: The official plugins use LTO. https://github.com/swc-project/plugins/blob/2324cb2aec86c2fa0cdd528f0edc7743cf259a86/Cargo.toml#L34 |
Describe the bug
For the tracking purpose.
After recent upgrade to wasmer@3, we are observing plugin execution failure if the plugin binary is compiled with LTO enabled.
We do not have any clue yet - just know disabling lto makes it work in general.
Input code
No response
Config
No response
Playground link
No response
Expected behavior
Do not panic / crash
Actual behavior
No response
Version
@latest
Additional context
No response
The text was updated successfully, but these errors were encountered: