|7 days ago||12 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.
What is XState used for?
9 projects | dev.to | 21 Jun 2022
replace global state managers like Redux or Vuex
Redux Best Practices
5 projects | dev.to | 19 Jun 2022
Redux is a library used for global state management, meaning if you have a piece of state that you want to access in different places of your app, you can use Redux to manage that state and make it easily accessible anywhere. The global state can be anything from logged-in user information to UI state such as theme, etc.
How to use React with Redux
5 projects | dev.to | 16 Jun 2022
Now go ahead and import createSlice from the same library and create a reducer with it. createSlice is a wrapper around the old API from redux which reduces quite some boilerplate when creating reducers.
Prevent Acid Redux with Redux Toolkit
3 projects | dev.to | 14 Jun 2022
This post is going to help you get rid of the acid Redux associated with trying to use vanilla Redux.
React - Clean Architecture - Redux Toolkit
5 projects | dev.to | 11 Jun 2022
Tech Explained - a low-level primer on frontend technology
1 project | dev.to | 9 Jun 2022
Implement state in React using Redux Toolkit (easy way🔥)
3 projects | dev.to | 8 Jun 2022
Redux is a library for managing and updating application state using events called actions. It serves as a centralized store for state, that needs to be used across your entire application(instead of props drilling), with rules ensuring that the state can only be updated in a predictable fashion.
Introduction of React Context
2 projects | dev.to | 8 Jun 2022
By using React Context, we make our code ma lot more concise. Which also eliminates the props drilling problem. Aside from React context, there are also another options available like Redux or MobX which is a global state management.
Why Is Front-End Development So Unstable? (2018)
5 projects | news.ycombinator.com | 30 May 2022
> > I maintain my 2017 apps including major version bumps with no issues today
> Sorry but I have to call bullshit on that, unless you’re taking about tiny one page “apps”
What a strange stance. It's a React/MobX collaborative model editing internal tool deployed in production to users who generate and analyze models with it. It started on Webpack 2 and React 15 and MobX 4, now it's on Webpack 5 and React 17 and MobX 6. I of course had to update some babel configurations but it was much more version bumping than configuration rebuilding. It still uses decorators and looks like complete dog-shit, and that's my point: the same tricks and patterns available then are not only there, but working identically now.
Re: native, I don't believe in React Native or any webview-based "native" replacement anyways, but it's easy to do this as my user-base is interacting with this app from their company-provided laptops anyways. I would willingly concede React Native is an environment with churn, I don't really recall RN every reaching meaningful stability
> Redux is dead in the water
https://www.npmjs.com/package/redux shows 7M downloads weekly
MobX / MobX React are around 1M/700k
Your list of "flummox / redux / unstated / mobx / mobx-state-tree / xstate / apollo / apollo-link-state / swr / react-query / zustand / recoil / jotai" seems to peak at 500k with the exception of "react-query", which I don't really see as applicable to a conversation about state management, and perfectly illustrates my point that there's new stuff but you don't need to know it
> you say it’s #1, but Redux is dead in the water
I never personally believed in Redux, it struck me as a terrible pattern from the start, thus why I selected MobX; but I find it difficult to believe that you really think React Context scales the same way building an external state management tree does. I like React Context, but it doesn't do a very good job of hiding away complexity from the developer as the application grows. Not to mention it does no render-optimization for you.
Again, I'm not saying things don't change or that there's not alternatives, but I am saying that someone who learned fundamentals in 2017 is still able to get up-to-speed in the updated versions of the library kings of 2017 in virtually no time, and deliver standard-fare webapps. I say this because I've worked at the same place for over 5 years, I use the same tools, and my users regularly are telling me the tools my team puts in front of them are the gold standard. The churn is long gone, everything you describe would have perfect analogues in any other popular modern language / library ecosystem.
Surprising Performance Lessons from React Microfrontends in Production
7 projects | dev.to | 22 May 2022
Use of global state management libraries e.g. Redux, MobX and XState.
What are some alternatives?
zustand - 🐻 Bear necessities for state management in React
pinia - 🍍 Intuitive, type safe, light and flexible Store for Vue using the composition api with DevTools support
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
SWR - React Hooks for Data Fetching
redux-toolkit - The official, opinionated, batteries-included toolset for efficient Redux development
swift-composable-architecture - A library for building applications in a consistent and understandable way, with composition, testing, and ergonomics in mind.
xstate - State machines and statecharts for the modern web.
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.
reflux - A simple library for uni-directional dataflow application architecture with React extensions inspired by Flux
kea - Production Ready State Management for React