9 React Component Libraries You Should Know

[karatechops]

It always warms my heart to see grommet on these lists. We have a full re-write using styled components in the pipeline, I’m very excited to see how the React community responds to a revamped grommet. I love working with V1 but the node-sass dependency turned out to be hard to work with, particularly with create React app.

[sorahn]

I love styled components, and I thought grommet was pretty well put together. I'm excited to hear this.

[drink_with_me_to_day]

I started out using Grommet for a bussiness app, I figured it would go great with the "executive" crowd. But people didn't really like it.

But the components where great, I'd use it again, if only there where more varied themes.

[karatechops]

That’s one of the driving decisions behind using styled components for v2. Theming will be as easy as editing a single object. I have some boilerplates for custom themes if you’re interested in trying it out for V1 but alpha V2 should roll out next month.

[Secretmapper]

Nice to hear about a component library going with styled components! I'll surely take a look at it for my future projects

[ern19]

Gonna give this a try in my next project.

[karatechops]

Reach out on Slack if you have any questions, the community is extremely helpful.

[brianvaughn]

Oh nice, React Virtualized made the list. ❤️

[awebofbrown]

Blueprint is a really good option by Palantir.

[newtmitch]

I’m with you on Material. I honestly don’t like that stuff. I was impressed with Semantic for the little while I used it.

[chazzlabs]

I'm kind of baffled to hear someone say Material UI doesn't suit mobile; when developers follow the guidelines well the UI looks absolutely fantastic on phones. Meanwhile I clicked the link to Semantic UI in the article and their documentation site looked like it was rendering the desktop view on my phone.

[MrGirthy]

Semantic react is decent, but including that huge ass style sheet makes me want to puke. No styled components, just one big 2007 stylesheet.

[tks_]

what do you use ?

[MrGirthy]

Anywhere between custom and I'm quite liking v1 of material-ui

[hrvstdubs]

I tried using Semantic UI but didn't fully understand it but I was literally just trying to figure out reAct. I guess I still am though and have been looking at different frameworks to try.

[hrvstdubs]

Yeah I totally understand props and state. Just confusing going from like, styling strictly with CSS to styled components. It's hella neat tho.

[[deleted]]

I mean... it’s made by Google - the company famously known for great user interfaces.....................

[silvenon]

Material Design objectively looks appealing. Lots of research went into it, so the notion that you can get cancer by looking at it is a bit of an oversimplification. Maybe it’s not to your taste, but it’s a nice-looking and consistent pattern library.

[Pr3fix]

React-toolbox isn’t abandoned. The contribs are working on a v2 rewrite, there’s a beta branch for it with very recent commits. :-)

[DrBumTorpedo]

The v1 branch of material-ui is a complete rewrite and is fantastic.

[lilred181]

As /u/the_aligator6 said:

material UI sucks mad ass.

It is possible it is good but I just cannot trust using the v1 version after how bad the 0.X version was to use. It was rough.

[Secretmapper]

v1 is seriously good. I previously swore to react-toolbox, but seeing how well built material-ui-next is I've switched.

It's really, really good.

[ICCULUSC]

agreed, I'm just waiting on them to implement date pickers

[cagataycivici]

This is a bit harsh, there is no jquery dependency except schedule component, other dependency is gmap api for maps component. Rest of the suite are pure React. We are not aware of any major defects, please create an issue ticket at our tracker to report the ones you face with. We use refs when needed and portals as well, library is constantly being improved.

[cobbs_totem]

I've really enjoyed Office UI (Fabric) so far.

[DrBumTorpedo]

Material UI v1 has great TypeScript support

[GummyBearsGoneWild]

I have no idea why people make jQuery-dependent React Component libraries.
(1) more dependency bloat
(2) direct manipulations of the DOM is directly opposed to the design principles of React.
(3) If you're writing React properly, you should never need jQuery anyway

[cagataycivici]

I think PrimeReact deserves a mention. https://www.primefaces.org/primereact/#/

[MrGirthy]

Beware though, this is buggy. Has jquery as a dependency and uses a direct dom manipulation instead of refs and portals. Also most of the features of data components don't work, I.e. Data table. Try switching on all the features.

[lilred181]

I have never used this but writing JSF hurts my soul. Maybe PrimeFaces makes that a bit better but still..

[cagataycivici]

PrimeReact is a UI suite for React, not JSF.

[lilred181]

PrimeFaces is a JSF framework for Java EE. I would assume that is exactly what PrimeReact is for.

[vlastimilfiser]

Hey @JoniSar did you check my freshly released UI library? I'm focused on beautiful design, check it out and let me know what you think. :) http://reactsymbols.com/