-
-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
Unable to run storybook after updating to 5.x, using css modules and sass. #9670
Comments
cc @mrmckeb |
Hi @Tasemu, are you using the new external preset for CRA? If not, please give that a go - and remove your custom Webpack config as it will conflict :) Sorry for the long delay, I was abroad. |
Hi @Tasemu, is this still an issue or can we close this off? Thanks! |
@mrmckeb following as I have the same issue but using CRA. My sass/scss is working fine from within this repository, however storybook build fails when I try to use a package from my node_modules where there is scss involved. Private repo for now or I'd share appologies. |
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! |
Describe the bug
When running storybook after upgrading to the latest version, i get console errors stating that it cannot understand my .module.scss files
To Reproduce
Run
npm run storybook
in CRA appExpected behavior
Runs storybook
Screenshots
Code snippets
webpack.config.js within .storybook
System:
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: