You no longer have to write React components with component logic and separator styles, but only with styles. What new developers might find difficult when starting to use this library is a different approach to mental models. It has support for TypeScript, media–queries, and Themes. Its well–written documentation and SCSS–like syntax make it easy to use and start for new developers. Styled components let you write CSS–in–JS styles. When it comes to styling a React component, you have some options: use traditional CSS or some of its preprocessors, CSS modules, inline styles, and CSS–in–JS. Both offer hooks, support TypeScript, and are developed by Poimandres, an open–source developer collective. Jotai works of an idea where every piece of state is an atom, where Zustand looks more like Redux with a global store.

Both libraries are lightweight and require minimal setup to work. That’s where Jotai and Zustand come to the rescue. Despite all that, there are cases where you need to have some values saved in global state, and using Redux feels like an overkill. Patterns like component composition and the introduction of React context and hooks made it easier to manage the global state and solve the issue of prop drilling. Redux was one of the first libraries that made it “easy” to manage global state, but since then, React has evolved. React and state management - this feels like a never–ending story.

It also has a lot of tools that make it easier to create store, actions, selectors, and even data fetching. It supports TypeScript and hooks out of the box.

The Redux team decided to create a tool that is opinionated and makes it easier to implement Redux in React applications. With time a lot of developers started to adapt it to their needs, which resulted in various implementations of Redux. When Redux, a predictable state container came around, it helped to handle all the global states in React applications.

Npm react