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
No conflicts with other components. But BEM quite good isolate CSS too
Ability to optimize CSS
We can remove unused CSS.
But actually no, due to dynamic use styles. I mean conditional use and use classes by dynamic names
Ability to analyze CSS
We can check custom CSS properties while compilation
No problem with Next.js
Now, global CSS on library level is not supported on next.js
But this is not problem of library, but problem of next.js design. The impossing a CSS modules/styled components on next.js side is not a reason to refactor library
Looks that CSS modules are useless for this UI kit
cn
library?.Menu ~ .Button
. Should we forward class name hooks?The text was updated successfully, but these errors were encountered: