In the beginning of the web it was really a very complete library with a lot of tools and functions that made it easy to do things in JS. But since Webpack and babel have been around, jQuery has become pretty outdated. A heavy library, which only allows you to do things that JaveScript can do natively. The ES6 functions are so powerful, and even in TypeScript you can do things more easily than jQuery is totally scooped up. There is no longer any point in using it
font-awesomeThe iconic SVG, font, and CSS toolkit
I think it's the only library to handle a large number of icons. This one is the most maintained. They update every 5 years (I mean a big update). The icons look great and offer several ways to use them. Via CDN / NPM, etc.
One of the most complicated React libraries I've ever used. Its documentation is very well provided, but Redux is really very complicated to learn and set up. Once this step is done, it is a very powerful tool to manage the states of your application. Whether simple or heavy, Redux is a great tool. You will obviously have to follow the best practices very precisely to prevent your application from crashing or using too much memory. Redux also has a very strong community which makes it easy to get help if needed. The holy grail for React.
gulpA toolkit to automate & enhance your workflow
A fairly complex tool which with each new version certainly brings new features, but also makes things obsolete. I had a really hard time using gulp properly until I discovered Webpack and even Webpack again. It is the latter that allowed me to remove gulp. It is true that Gulp is a very powerful tool and that a lot of plugins exist for Gulp, but the choice to learn how to use Gulp is yours. The documentation is rather well supplied.
serveStatic file serving and directory listing
You need an easy server to test your react app (or even HTML pages) here's serve. In one command it boot up a lovely server on your localhost, on a specific port (if the default one doesn't suits you).
Your app will work just as in produciton. It can be used to list files in a specific directory either.
Simply to use, easy to set up.
I recommand to download it as a global package and not as a project dependency
I had to use this front end framework in a project, and I have to say docs are really god, there are tutorials to get started as well. It's really powerful and easy to use. Of course, it evolves rapidly, but like any other framework. If you don't know which one to use, React is pretty straightforward to use, and there are plenty of libraries out there to improve React!
The best compiler out there. Its use is complex and its execution times can be long when you have a lot of rules and plugins, but it is more than worth it. It's the second I've used after Gulp, and I have to say it does pretty well what you ask it to. In addition, a lot of plugins are webpack compatible, which makes it easy to create bundles in a few clicks.
react-adminA frontend Framework for building B2B applications running in the browser on top of REST/GraphQL APIs, using ES6, React and Material Design
I needed to implement an administrator connected to a REST API (using the API platform). The React administrator is easy to set up and connecting to your API is easy. Of course, React Admin needs your API to meet standards, but once that's done, you can do some magic. Implemented with React and Material-UI this is the best admin I have ever found
yall-jsA fast, flexible, and small SEO-friendly lazy loader.
YallJS is a library that allows you to lazyload your images or even videos, inline or in the background. This puging makes your site more efficient, but is also SEO compatible. That is to say that Google will know how to see that you have these images on your site. The developer indicates that the development of the plugin is finished.
yarnThe 1.x line is frozen - features and bugfixes now happen on https://github.com/yarnpkg/berry
I choose to migrate from npm to yarn because it is a really better alternative. It's performant, the way it handles package download is less messy than NPM. But now with the improvements of npm, it doesn't matter which one you wnat to use, they're pretty the same. But Yarn handle better the .bin to execute packages