Ryan Christian

@ThunderArmy Have you added another version of `postcss-loader`?

@ThunderArmy Ah, yeah, storybook pulls in another version. You might need to use another version of storybook, or, if you can, try it with Yarn. On my own system, Yarn...

I've never touched storybook, but we enable CSS modules for `routes/` and `components/` directories automatically [here](https://github.com/preactjs/preact-cli/blob/4b8164172ec4e7e9a725909b58bc54eb1f82ed8a/packages/cli/lib/lib/webpack/webpack-base-config.js#L242-L269). I'm not sure how storybook works. You run a separate CLI with it, right?...

Have a repo you can share? I can try to take a look soon here after I finish dinner.

Sorry, but what do I need to do here to reproduce your issue? You seem to have no CSS module usage in your storybook stuff?

Gotcha, was looking in `stories/`. My bad.

@ThunderArmy Sorry for the delay, got side tracked. I just did a quick search and it seems like someone's created a package to do this, worked with a simple install...

> I know it's been a while since you posted this but I was hoping you could explain this step.. > >> * define my own entry based on [this...

Thanks! Want to write up a PR fixing this? Reminded me of #1424 which looks to be the same issue.

I imagine it's due to the `optimize-css-assets` plugin. Can you try adding the following into your `preact.config.js`? ```js // preact.config.js export default (config, env, helpers) => { if (env.isProd) {...