nanostores
effector-react
Our great sponsors
nanostores | effector-react | |
---|---|---|
17 | 26 | |
4,739 | 4,491 | |
4.6% | 1.1% | |
8.4 | 9.4 | |
6 days ago | 6 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.
nanostores
-
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.
-
React roadmap ( with explanations and resources, all in one place)
Nanostores explanation
-
How to Write a Great Readme
vidstack is very light on technical details but starts with a concise intro and a screenshot, as well as relevant links: https://github.com/vidstack/player
payload is well-structured in general: https://github.com/payloadcms/payload
nanostores starts out with an intro and telling code examples, followed by lots of technical details: https://github.com/nanostores/nanostores
-
Is redux and thunks still used or are there other alternatives for it now?
Nanostores and Reatom are also great, fast atomic libs
-
Is it possible to build a “framework agnostic” library like tanstack table?
Astro handles multi-framework components (React, Vue, etc) and they recommend using the nanostores library for shared state.
-
how to share state between components with distant shared parent?
Checkout Nanostore it's what Astro.build recommends for sharing state across different ui libraries.
-
Building a multi-framework dashboard with Astro
All of these are valid ways of fixing the state management issue, but it's clear that we need to find a common solution that works for all the UI libraries. This is where nanostores comes into play! The description they provide on their GitHub page is simply perfect:
- A tiny state manager for React/Vue/Svelte with many atomic tree-shakable stores
-
Explanation on how Redux or React Context could help and picking the best option
Jotai and Valtio are both also really good. Recently looked at Nanostore as well and has some similarity to Jotai and Recoil.
-
My next project will use this Ui lib...
Just to chime in on framework agnostic stores, Astro.build recommends using Nano Stores to handle reactivity, as the base library is very small and they have adapters for most relevant frameworks. I definitely agree that avoiding framework lock-in is the smart thing to do.
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?
jotai - 👻 Primitive and flexible state management for React
pinia - 🍍 Intuitive, type safe, light and flexible Store for Vue using the composition api with DevTools support
nanoid - A tiny (124 bytes), secure, URL-friendly, unique string ID generator for JavaScript
redux - A JS library for predictable global state management
zustand - 🐻 Bear necessities for state management in React
mobx-react
nextjs-course-code - Source code for my NextJS course (https://acad.link/nextjs)
create-figma-plugin - :battery: The comprehensive toolkit for developing plugins and widgets for Figma and FigJam
SWR - React Hooks for Data Fetching
reselect - Selector library for Redux