Echo JS 0.11.0

<~>

xat 2568 days ago. link 1 point ▲ ▼
The CSS solutions in React are really fragmented. Every few months there is a new hotness in town. Reminds me a bit of all the Flux-like libraries which existed in the pre-redux period. Personally, I tend to just use plain CSS with some BEM notation. I know, it's old school, but I'm sure it won't be outdated in 5 years from now. In the company we are settling for styled-components though.
tracker1 2567 days ago. link 1 point ▲ ▼
I've either gone with Sass (via webpack/require) per component, or with JSS (my preference lately)... react-jss works pretty well, and I can always start with inline, change to jss as I go.  Some things are a bit awkward starting out, but it's easier to share configs and common settings with JSS.  My only complaint is the library is a little heavy.
xat 2566 days ago. link 1 point ▲ ▼
Thanks, I'll have a look at React-JSS. Even if it fragments CSS in react even more :)
tracker1 2563 days ago. link 1 point ▲ ▼
Yeah, I was really interested in Aphrodite, but react-jss just seems slightly better in terms of a solution.  It renders to style tag(s), so you can do media queries, and you can invert nesting similar to sass/less, so it's not bad.. remembering to quote css properties is the only hard part (similar to inline)... you get classes to set on your rendered components, similar to aphrodite (iirc), and it goes well enough.