Re: [w3c/webcomponents] CSS Modules (#759)

To add customer requests for the use-case I'm referring to:

We have a current Polymer customer who is using a feature we call "style includes" which are basically a direct replacement for `@import` (a `<style>` tag can include another style with an `include` attribute. We do this so we can process the styles for polyfilling) ask to be able to dynamically replace a certain include across their app in order to implement theme switching.

It would be very natural to do this with CSS modules with Option 3 and `@import`. With Option 2 they would have to import all switchable/base styles directly via the JS module system, rather than use `@import` in CSS. This would hurt the ability to refactor the base styles because each JS module has to import all transitive CSS dependencies as direct dependencies, rather than getting them transitively via their immediate CSS imports.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webcomponents/issues/759#issuecomment-491474158