|6 days ago||3 days ago|
|MIT License||MIT License|
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
React state management libraries in 2022
8 projects | reddit.com/r/reactjs | 18 May 2022
classList API in forest
1 project | dev.to | 4 Apr 2022
New API allows to setup each class independently. Proposal. It is based on browser API classList.
Honestly, what is the best, pain-free state management in React right now?
16 projects | reddit.com/r/reactjs | 23 Feb 2022
What are the production ready alternatives for Vuex with full TS support for Vue2 ?
3 projects | reddit.com/r/vuejs | 27 Oct 2021
https://effector.dev/ We use it on production in several projects
The best part of Effector
2 projects | dev.to | 3 Oct 2021
To understand this part of the article, it is better to read Effector’s documentation first. Effector has a game-changer feature — Fork API. To understand it, we should talk about one important concept — scope.
Show HN: React Oxide: minimal in-browser code editor with tabs and files
5 projects | news.ycombinator.com | 29 Sep 2021
The issue with using eventemitter for state coordination is that when the UI grows into complexity you run into race conditions where some component isn't showing the right data because it got mounted too late or something somewhere up the hierarchy changed a key and the component got recreated and its state got lost.
I guess as long as long as the component hierarchy fits in your head, it is likely straightforward to reason about all the event interactions.
The lifted state model ala redux (and similar alternatives) doesn't suffer from this problem.
I personally prefer effector  these days because it combines the convenience of event emitter with multiple stores and you usually find yourself thinking much less about what changed the store causing my component to rerender much less often.
Best Store Option for Vue3 with Typescript
7 projects | reddit.com/r/vuejs | 13 Sep 2021
It’s worth noting that there is a thing called Effector and I have heard a lot of good stuff about it. Maybe you should give it a try and take a peek at its documentation as well.
Recoil, MobX, React Query which one to choose for serious project
3 projects | reddit.com/r/reactjs | 25 Jun 2021
Personally I'm finding Effector to be very useful for the kinds of projects I'm working on. It encourages small atomic stores which means you don't need selectors to avoid rerenders throughout the app. Effectors stores also handle updates from multiple dependent async effects and derived states really well.
Nano Stores: tiny state manager for React/Preact/Vue/Svelte in 152 bytes (!) and with tree-shaking support
This looks really cool to me and reminds me a lot of Effector, and looking at one of the open issues it seems that you are aware of it. Does this project have goals that specifically set it apart from Effector? You seem to lead with bundle size as a defining characteristic. Is that your long term goal? You seem to have plans to handle effects. How similar or different will that be from Effector?
The simplest React state manager now at stable release
6 projects | news.ycombinator.com | 20 Apr 2021
I found effector after I started looking around for a state manager which:
1. Either supported multiple stores or provides a way to subscribe to individual branches (as opposed to the entire store).
2. Had an action/event abstraction similar to redux where multiple branches (or multiple stores) could subscribe to the same action and update independently (and without knowledge of invoker).
I have been using it for some time and have had a good experience.
The core is framework agnostic (with additional integrations for react & vue).
I started used it with Svelte and its API matches the expectations of Svelte stores so you can use it without needing any additional integration, which was cool. Later I used it with lit-element through a 5 line custom integration and that worked pretty well too.
Friend tells me to apply, but I don't think I am ready...
1 project | reddit.com/r/reactjs | 23 Jun 2022
I introduced my team to jotai. https://jotai.org/
why react has a huge community?
6 projects | reddit.com/r/webdev | 19 Jun 2022
This has allowed a vast ecosystem of amazing libraries to flourish and support React in a way that benefits everyone. It might be annoying for some people to have to install any libraries to get an application running. And it might be annoying to have "17 state management libraries". But this diversity allows a particular place for all mental models of thinking. Some people might prefer Zustand, others might prefer Valtio or Jotai to store their data. All three of these state management libraries are created by the same group Poimandres.
Jotai – primitive state management within React
2 projects | news.ycombinator.com | 23 Apr 2022
4 projects | reddit.com/r/SideProject | 3 Mar 2022
Top Seven Reasons for using Redux toolkit
3 projects | reddit.com/r/reactjs | 2 Mar 2022
Would you recommend Recoil on a production application?
3 projects | reddit.com/r/reactjs | 25 Feb 2022
recoil - jotai
Composable Reusable Components with Jotai
2 projects | dev.to | 21 Feb 2022
Part of a strong codebase is the tooling that has been built to augment work within the environment, and reusable components play a significant role. Well-designed common code can be the difference between enjoyable development and a massive headache, and is something I'm always trying to find new ways to think about. I recently began working with Jotai for state management, and it has led to some interesting patterns for composition in reusable React components. If you're not familiar with Jotai, you can check it out here, or keep reading; it's not too complicated!
When I Use Valtio and When I Use Jotai
5 projects | dev.to | 2 Feb 2022
(noob) Can I use NextJS this way
2 projects | reddit.com/r/nextjs | 13 Jan 2022
So if you're alluding to "prop-drilling" (the unpleasant practice of passing data from a root component into deeper and deeper component context), then what you need is React's Context API. Here's an article which explains the problem and implements the solution. It's worth noting that the base Context API is a bit cumbersome on it's own, so I would recommend a CQRS state management library like Jotai. Just be sure to to add the special configuration step for use with Next.
A rare event that makes us all happy
2 projects | reddit.com/r/ProgrammerHumor | 9 Jan 2022
What are some alternatives?
pinia - 🍍 Intuitive, type safe, light and flexible Store for Vue using the composition api with DevTools support
zustand - 🐻 Bear necessities for state management in React
Recoil - Recoil is an experimental state management library for React apps. It provides several capabilities that are difficult to achieve with React alone, while being compatible with the newest features of React.
react-query - 🤖 Powerful asynchronous state management, server-state utilities and data fetching for TS/JS, React, Solid, Svelte and Vue. [Moved to: https://github.com/TanStack/query]
valtio - 💊 Valtio makes proxy-state simple for React and Vanilla
redux-toolkit - The official, opinionated, batteries-included toolset for efficient Redux development
react-hook-form - 📋 React Hooks for form state management and validation (Web + React Native)
redux-thunk - Thunk middleware for Redux
hookstate - The simple but very powerful and incredibly fast state management for React that is based on hooks
reselect - Selector library for Redux