Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →platformplatform/swc-plugin-compatibility
Diagnose and fix Lingui SWC plugin compatibility errors with Next.js, Rspack, or other SWC runtimes.
Passed 23 of 23 test cases with the skill, and 15 of 23 without it.
and 8 more in the full report
8 fixed15 passed either way0 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
When discussing SWC plugin compatibility in modern JavaScript tooling, what does the term 'runtime' refer to in this context?
| Checked | Without skill | With skill |
|---|---|---|
| Defines runtime as the execution tool running SWC, such as Next.js, Rspack, or `@swc/core` | Missed | Passed |
The instructions your model reads when the skill loads.
If you see errors like these during your build:
failed to invoke plugin on 'Some("/app/src/file.ts")'
failed to run Wasm plugin transform
RuntimeError: out of bounds memory access
LayoutError called Result::unwrap()
This is NOT a bug. You're using an incompatible version of @lingui/swc-plugin with your SWC runtime.
SWC plugin support is experimental. The plugin API does not follow semantic versioning.
SWC uses Rkyv to transfer the AST between the core and plugins. Both must agree on the exact memory layout of the AST. If the layout changes (e.g., new ECMAScript features), older plugins cannot read the data correctly.
This layout cannot be negotiated at runtime - it must match at compile time.
Go to the compatibility table and find the plugin version that matches your runtime.
For precise matching, use https://plugins.swc.rs/:
next)[email protected])@lingui/swc-plugin version{
"devDependencies": {
test cases passed, vs 15 / 23 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.