Even newly created SWC plugins cause Segmentation fault
run by Next.js
#5574
Answered
by
kwonoj
rinarakaki
asked this question in
Q&A
-
I'm getting the segmentation fault by the following steps. How can I solve this? Segmentation fault
swc plugin new --target-type wasm32-wasi test
{
"main": "test.wasm",
}
cargo build-wasi --release
cp path/to/test.wasm path/to/main
npm install --save-dev ./path/to/plugin
export default {
experimental: {
swcPlugins: [
['test', {}]
]
}
}
npm run dev |
Beta Was this translation helpful? Give feedback.
Answered by
kwonoj
Aug 21, 2022
Replies: 3 comments 1 reply
-
Did you try |
Beta Was this translation helpful? Give feedback.
0 replies
-
Thank you for your suggestion, and here is the output after I did Caused by:
Plugin runner cannot detect plugin's schema version. Ensure host is compiled with proper versions',
...
error - ./node_modules/next/dist/client/dev/amp-dev.js
Error: failed to process failed to invoke plugin: failed to invoke plugin on 'Some("/path/to/node_modules/next/dist/client/dev/amp-dev.js")' |
Beta Was this translation helpful? Give feedback.
0 replies
-
We will update next-swc to keep up with recent changes of swc/core soon, expect to have it in nex.js canary release. |
Beta Was this translation helpful? Give feedback.
1 reply
Answer selected by
kwonoj
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We will update next-swc to keep up with recent changes of swc/core soon, expect to have it in nex.js canary release.