Kai Tran

@philo23 yes, it'll be really helpful if you provide a repo, [codesandbox](https://codesandbox.io) or something to reproduce the issue

Hi everyone, sorry for the late response I've noticed my webpack example was erroneous and as a result all stylesheets got downloaded without respecting the current viewport. Therefore I've worked...

> @felixfbecker Could this maybe be an option of the plugin, to support this approach for folks whose constraints match this? I know it's been a while ago but would...

Hi @davidhouweling thanks for reporting this! you're right, it should use the entry name for the extracted CSS and not the imported filename – I'll try to fix it as...

> how to correctly map from the plugin via interpretName You mean `interpolateName`, don't you? (I've no idea what `interpretName` is) However I know the reason for the issue now:...

Many thanks for your research! > though it's quite difficult to understand given the amount of internal webpack plugins it uses yup, I was facing the same problem > One...

> What are your thoughts on dropping the loader all together and doing everything through the plugin? In general I'm a friend of getting rid of the loader so that...

> wouldn't it be doable to simply chain on from there? before writing my own plugin I actually thought abt extending the mini-css-extract-plugin – without success https://github.com/webpack-contrib/mini-css-extract-plugin/issues/162 I agree my...

Hi @jantimon > So you could split the files generated by mini-css-extract-plugin whenever they are generated or regenerated. This sounds great! Actually I've plans to bind my plugin more to...

> Yes that's exactly what I had in mind about the `mini-css-extract-plugin`. Ok, I need to check the code more in detail to know if/how this can be achieved. Feel...