Our great sponsors
-
SurveyJS
Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
I would actually be very interested in having you at try out that new "listener middleware" and give us some feedback on how it compares with using sagas. I'm not asking you to go rewrite your whole app :) But our goal has been to replace maybe 75% of the things that users could do with sagas, and so I'm really curious to see if we've managed to accomplish that goal.
That being said, I recently used Zustand for two bigger apps and I have to admit it's amazing. Performance is pretty neat (so far) and the state is already quite complex, but still greatly managable (and expandable).
You can have a look at mine :) educe.js
Redux + saga-query
Um, hello, MobX? You don't have to like it but it has 6x the weekly downloads as Recoil does, so it should at least be mentioned.
Nope, react-easy-state is much easier: https://github.com/RisingStack/react-easy-state
EffectorJS
To be clear: this is not a made up problem. There is a React RFC on the topic since June 2019, there is an experimental PR to the React codebase for this since January 2021. There are external packages like use-context-selector to work around it. As of today, there is no efficient way of partially subscribing to context value changes that is a native part of React.
To be clear: this is not a made up problem. There is a React RFC on the topic since June 2019, there is an experimental PR to the React codebase for this since January 2021. There are external packages like use-context-selector to work around it. As of today, there is no efficient way of partially subscribing to context value changes that is a native part of React.
To be clear: this is not a made up problem. There is a React RFC on the topic since June 2019, there is an experimental PR to the React codebase for this since January 2021. There are external packages like use-context-selector to work around it. As of today, there is no efficient way of partially subscribing to context value changes that is a native part of React.