-
-
Notifications
You must be signed in to change notification settings - Fork 9.4k
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
Webpack error "loose module configuration must be the same" #12093
Comments
Was able to work around this using babel/babel#11622 (comment) : explicitly adding both addins |
Hi everyone! Seems like there hasn't been much going on in this issue lately. If there are still questions, comments, or bugs, please feel free to continue the discussion. Unfortunately, we don't have time to get to every issue. We are always open to contributions so please send us a pull request if you would like to help. Inactive issues will be closed after 30 days. Thanks! |
Hey there, it's me again! I am going close this issue to help our maintainers focus on the current development roadmap instead. If the issue mentioned is still a concern, please open a new ticket and mention this old one. Cheers and thanks for using Storybook! |
Related issues: - Removed @babel/plugin-proposal-class-properties plugin. Not sure this is the right thing to do, I'll try to find another workaround storybookjs/storybook#12093 - Added some core-js magic things in the storybook webpack configuration. storybookjs/storybook#11255 (comment)
Related issues: - Removed @babel/plugin-proposal-class-properties plugin. Not sure this is the right thing to do, I'll try to find another workaround storybookjs/storybook#12093 - Added some core-js magic things in the storybook webpack configuration. storybookjs/storybook#11255 (comment)
Related issues: - Removed @babel/plugin-proposal-class-properties plugin. Not sure this is the right thing to do, I'll try to find another workaround storybookjs/storybook#12093 - Added some core-js magic things in the storybook webpack configuration. storybookjs/storybook#11255 (comment)
I was able to work around this error message by upgrading the versions of all my |
I was able to solve this via. Yarn resolutions:
|
The way I solved this, using Storybook v6.29, was adding the following into module.exports = {
babel: async options => ({
...options,
plugins: [
'@babel/plugin-proposal-class-properties',
'@babel/plugin-proposal-private-methods',
],
}),
// ... other settings here
} |
I tried the things mentioned above, but they did not work for me. Upgrading all Now I still get a warning, but I can start storybook... 🥳
Coming from upgraded to
Hope this helps someone... 😄 |
Using Storybook 6.3.8 and this fixed my issue. Thank you. I also had to make sure I had the plugins listed in my
|
Along with adding resolutions in package.json, what worked for me was to provide a custom
|
Describe the bug
I upgraded storybook from v5.3.19 to 6.0.12, and I'm seeing this error at startup time.
To Reproduce
Steps to reproduce the behavior:
Ran
yarn upgrade --latest -S @storybook/
Somewhere buried in our standard
babel.config.js
we specifyBesides being somewhere in our package.json, we don't otherwise use the
loose
flagScreenshots
The precise error message is:
Code snippets
I've created a
.stroybook/.babelrc
which containsIn addition, I've ensured that my
yarn.lock
file has no uses of babel < v10.5, which is when babel/babel#11622 was reported as fixed. I saw several people complain about this for pre-release storybook 6, but not for post-release. (Congratulations, btw, on the release!)System:
The text was updated successfully, but these errors were encountered: