CSS @import throws error about storybook-addon-next HOT 6 CLOSED

Thanks for opening the issue!

The pull request above fixes the error although I'm not happy with the solution. I think there is a better one I'm missing. The details are spelled out in the pull request description.

By any chance do you have insight?

from storybook-addon-next.

By any chance do you have insight?

Sorry, I don't

from storybook-addon-next.

@RyanClementsHax Thanks for resolving this so quickly!

from storybook-addon-next.

So it turns out that @storybook/builder-webpack4 includes css-loader v3.x in its dependencies. Because of this, the resolved version of css-loader used is v3.x.

Because @storybook/builder-webpack4 is included from installing core storybook packages like @storybook/addon-essentials and @storybook/react, I'll just use the solution mentioned.

@RyanClementsHax Thanks for resolving this so quickly!

No problem!

from storybook-addon-next.

🎉 This issue has been resolved in version 1.4.2 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

from storybook-addon-next.

@RyanClementsHax Thanks for more details about the issue. I've had issues on previous storybook setups with different css-loader versions and storybook conflicting. Think I even moved everything relating to storybook into it's own project, just so we didn't have to deal with npm package conflicts in production.

It's also an issue when you use the storybook-preset-scss. Depending on the webpack version you have to install different webpack loaders. But this information isn't highlighted in the main README

webpack 4
https://github.com/storybookjs/storybook/blob/a3433c17a08d0ca8debd14f685ef4a040c77837e/docs/snippets/common/storybook-preset-scss.webpack-4.js.mdx

webpack 5
https://github.com/storybookjs/storybook/blob/a3433c17a08d0ca8debd14f685ef4a040c77837e/docs/snippets/common/storybook-preset-scss.webpack-5.js.mdx

There is also an issue with the wrong version of webpack resolving on a storybook install. Which I think is to do with npm versions and how it resolves dependencies. You can get different outcomes on a new npm install without a package-lock.json file 👎🏻
storybookjs/storybook#15336 (comment)

from storybook-addon-next.