Modularity for CSS #354
Cleanshooter
started this conversation in
Ideas
Replies: 1 comment 3 replies
-
Until V3. Bulma was included on the library but we decided to exclude it because of the difficulty of setting it up in a way that allow overwriting the sass variables. You can check it here https://github.com/couds/react-bulma-components/tree/v3.4.0 We also perform a pool about that https://doodle.com/poll/mqqpxwkzm6nnrs3s |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
One thing I noticed the other day while doing some basic performance testing with lighthouse was that Google is complaining about including CSS that isn't being used. At the time I saw it I kinda blew it off (my app is still in the early development stages) but when I looked further I saw that it was actually complaining about the unnecessary CSS from bulma.css.
It got me thinking, 'Is there a way to slim this down?"
In the past I've used tools like CSS Modules to load CSS for a component when it's needed rather than loading all of it all the time.
Then I decided to look into it more and it seems that even Bulma supports this concept OOTB: https://bulma.io/documentation/overview/modular/
So I'm curious what people think about including Bulma as a project dependency and "in-lining" the CSS to each of the components. I know it'd be a big change but I'm curious what people think about the approach. I'd love to contribute to the effort but I don't want to start if there isn't any interest.
Beta Was this translation helpful? Give feedback.
All reactions