nanostores
valtio
nanostores | valtio | |
---|---|---|
17 | 47 | |
4,772 | 8,468 | |
2.6% | 1.7% | |
8.4 | 7.6 | |
4 days ago | 2 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.
valtio
- 5 Alternatives to Redux for React State Management
- How to properly structure a valtio shared state object?
-
Changelog #0023 — 🛠️ Internal refactoring and improvements
We took inspiration from the many frameworks we worked with throughout our careers. And maybe surprisingly, Django’s ORM layer impacted our design choices and the API quite a bit. The resulting framework relies on Zod for schemas and validation and Valtio for React integration.
-
Is redux and thunks still used or are there other alternatives for it now?
Valtio is like simplified MobX
-
Why is building a UI in Rust so hard?
Even simpler than Zustand are state-atom libraries like jotai or recoil, or proxy based ones like valtio. Here's some discussion about the differences.
-
How to implement state management inside a simple JavaScript app
There is a package developed around this proxy concept called Valtio which is available for JavaScript, React, and so on... feel free to check and star it on Github.
-
What is being used right now for ioc/state-managment?
I'm switching from redux-saga to valtio (https://github.com/pmndrs/valtio) for now. It's simple and easy to use, everything's great so far.
-
Ask HN: What is your favorite front end state management solution?
I like valtio, works w/ React or just js. Has subscribe, derive, and more.
https://github.com/pmndrs/valtio
-
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.
-
Notes on LiveView Components and JS interactions
Since we want the React component to react to an external change, using a state manager makes this easy. We will use Valtio here by example. For this library, change the esbuild config to --target=es2020 instead to remove some warnings (for example, the Zustand library is ok).
What are some alternatives?
jotai - 👻 Primitive and flexible state management for React
redux - A JS library for predictable global state management
effector-react - Business logic with ease ☄️
MobX - Simple, scalable state management.
nanoid - A tiny (124 bytes), secure, URL-friendly, unique string ID generator for JavaScript
zustand - 🐻 Bear necessities for state management in React
Immer - Create the next immutable state by mutating the current one
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
leva - 🌋 React-first components GUI