robodux
effector-react
robodux | effector-react | |
---|---|---|
2 | 26 | |
100 | 4,491 | |
- | 0.4% | |
4.1 | 9.4 | |
7 months ago | 8 days ago | |
TypeScript | TypeScript | |
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.
robodux
-
Ask HN: What is your favorite front end state management solution?
Like most systems, it’s all about how it is setup. I’ve learned over 5-7 years how to organize FE (with redux) code so it is readable. Also inheriting a system can be quite the burden and I could see how it was be difficult to grok.
I also heavily leverage https://github.com/neurosnap/robodux to treat redux as a database.
At the end of the day, redux is an event emitter (pub/sub) with a single object that stores all of your state that multiple components need to reuse.
- robodux: a powerful middleware and caching library for redux side-effects
effector-react
-
Astro.js as an alternative to Next.js: pushing the limits
In its docs, Astro recommends nanostores, but I’ve used effector in the past. And LOVED IT. So I’ve used it for this project as well.
-
Global, reactive data store vs local, colocated graphql query?
I've been using effector, together with the apollo-client for the last few years and, while it works, it's completely detached from the actual screens. In other words, you need to fetch everything (at startup) you might use at some point and it stays in the memory for the entire duration of the session. Error handling is also tricky as you need to explicitly subscribe to the specific error stores in order to render them. And, if something goes wrong, it's tricky to tell what data is actually used in the current screen, so it's almost impossible to do the Retry efficiently. OTOH the screens are nice and simple - no spinners, the data is just there, thus the app feels (and is) fast.
-
Ask HN: What is your favorite front end state management solution?
Actually, Svelte uses Effector for state management under the hood. You can read more about it here: https://effector.dev/. It also has bindings for other frameworks including React, Vue and Solid. Effector is a little not beginner-friendly, but once you truly understand it, Effector becomes a very powerful.
-
So what is Effector ?
A state-management library.
-
So what is Effector ☄️ ?
Effector it is the another way to create state and business logic for your frontend application.
- [Question] Recommendations for an agnostic state management?
-
What concepts of react are the most difficult to understand ?
https://effector.dev/ here you go
-
I need some advice for my next tech stack
Then I found Effector which seems to have the same features, and SolidJs support.
-
The new wave of React state management
Where’s effector?
-
React state management libraries in 2022
https://ngneat.github.io/elf/ https://effector.dev/
What are some alternatives?
wrmhole
pinia - 🍍 Intuitive, type safe, light and flexible Store for Vue using the composition api with DevTools support
valtio - 💊 Valtio makes proxy-state simple for React and Vanilla
redux - A JS library for predictable global state management
saga-query - Data synchronization using a middleware system for front-end apps
mobx-react
htmx - </> htmx - high power tools for HTML
jotai - 👻 Primitive and flexible state management for React
zustand - 🐻 Bear necessities for state management in React
nanostores - A tiny (286 bytes) state manager for React/RN/Preact/Vue/Svelte with many atomic tree-shakable stores