You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If any plugins are specified via the use option, class names will not be scoped. Worse yet it's not plugin specific because an empty array still results in no scoping of classnames.
You're right @themitchy , this is a bit confusing because it doesn't make so much sense if use drops the very plugins that make css modules work. We hope to address this point (and some others) when we go to v1.0 (discussion in #29)
If any plugins are specified via the
use
option, class names will not be scoped. Worse yet it's not plugin specific because an empty array still results in no scoping of classnames.css:
plugin configuration:
With the above the generated css is:
With
use: [ ]
the class name is still not scoped. Withuse
completely removed the class will be scoped correctly.Seems like css-modules + plugins is too common a use case to not support it.
The text was updated successfully, but these errors were encountered: