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
Breaking change in recent version #32
Comments
@lesha1201 The relevant error seems to occur when going through the following process. However, I don't have much knowledge of Rust, so I am not sure why this process is being executed. I will close this issue for now and re-open it if many others seem to encounter the same error. |
I have the same issue after upgrading from |
We are experiencing same issue with 1.1.7 addon, seems to work fine with latest swc and loader with 1.1.5 addon Not working: "@swc/core": "1.2.203",
"storybook-addon-swc": "1.1.7",
"swc-loader": "0.2.3", Working: "@swc/core": "1.2.203",
"storybook-addon-swc": "1.1.5",
"swc-loader": "0.2.3",
{
"env": {
"targets": {
"chrome": "90"
}
},
"jsc": {
"parser": {
"syntax": "ecmascript",
"jsx": true
},
"target": "es2020"
},
"minify": true
} |
Same thing with EDIT: I fixed it by configuring {
name: "storybook-addon-swc",
options: {
swcLoaderOptions: {
isModule: true, // This fixed my build
module: {
// Our storybook build needs commonjs, otherwise it won't compile properly.
// NOTE: Other GitHub users reading this might not need it.
type: "commonjs",
},
},
},
}, |
The small number of people encountering the same problem makes me wonder if the swc settings of the person using it are simply incorrect. By the way, the default value of isModule is false, not true. |
Hello! I've recently tried to upgrade from version
1.1.1
to1.1.7
and the build were failing with errorError: failed to handle: not implemented: automatic polyfill for scripts
:I noticed that
isModule
were changed toisModule: 'unknown'
in this commit ed714ba. Changing it back to the default valueisModule: true
fixes it.I don't know why it doesn't work with
isModule: 'unknown'
but letting you know about this issue and how it can be fixed if someone encounters it.Info:
Swc config:
The text was updated successfully, but these errors were encountered: