nanostores
valtio
| nanostores | valtio | |
|---|---|---|
| 22 | 55 | |
| 7,413 | 10,191 | |
| 2.1% | 0.2% | |
| 7.8 | 8.3 | |
| about 1 month 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.
nanostores
-
NanoStores: A Tiny Redux Alternative for React, Vue, Svelte, and More
[1] Nano Stores GitHub. https://github.com/nanostores/nanostores
-
How does one build large front end apps without using a framework like React?
I build a lot of micro sites, but I still use frameworks — like Deno (node alternative), Hono (for APIs), and Alpine.js (for tiny lightweight sites).
you don't have to though!
if you want to do more pure vanilla, understanding signals is really useful — this basically powers svelte's runs and react's hooks and whatever.
I love nanostores, a 286 byte (!) state manager that lets you build highly reactive pages w/o the weight: https://github.com/nanostores/nanostores
flexible tools like tinybase (https://github.com/tinyplex/tinybase) and unstorage (https://github.com/unjs/unstorage) are also super useful
tools like this lets you build highly reactive, engaging sites that load for under 50-100kb
-
Using nanostores in Astro + Vue setup
use a shared state manager like nanostores
- Nanostores: A tiny (286 bytes) state manager for React/RN/Preact/Vue/Svelte
-
Building jargons.dev [#2]: The Dictionary Search Engine
I retrieved access to files the directory of words using the Astro.glob() function super easily (too bad I couldn't talk about how powerful this function is; how glad I am it existed out-the-box in Astro and how much ease it brought into the flow of getting this search engine up and running) and plugged the returned array of word objects into a $dictionary state (maybe I should call this a store) powered by nanostore (another beautiful stuff right there)
-
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.
valtio
-
JavaScript Awesome Package
Valtio - Valtio makes proxy-state simple for React and Vanilla
- Ripple is a TypeScript UI framework (If React and Svelte would have a baby)
-
Valtio: The Proxy-Based State That Makes React State Management Feel Like Magic
Valtio Official Repository. https://github.com/pmndrs/valtio
-
Show HN: Aberdeen – An elegant approach to reactive UIs
Oh.. yeah, the proxy part does look really familiar! :-)
Also, their use of promises looks interesting: https://github.com/pmndrs/valtio?tab=readme-ov-file#suspend-... -- I might borrow some ideas from that... :-)
-
Creating a library for both React and Vue 🤝
I explored libraries like Valtio and Mitosis, but neither fit perfectly. I didn’t want to add a peer dependency for Valtio, and Mitosis didn’t work well with a shared context.
-
React v19 has been released
The people behind Jotai also made Zustand and Valtio:
https://github.com/pmndrs/zustand
https://github.com/pmndrs/valtio
To me it feels like Jotai has too much manual boilerplate and Valtio has a lot of "magic" that while I do like it I don't feel like it would be a good idea for a team. Zustand sits right in the middle of boilerplate-vs-magic, and is what I chose for a large project we're doing now.
-
Supabase uses Valtio for its state management
As I was reading the Supabase source code for “fun”, I came across a package named 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.
What are some alternatives?
jotai - 👻 Primitive and flexible state management for React
MobX - Simple, scalable state management.
effector-react - Business logic with ease ☄️
Immer - Create the next immutable state by mutating the current one
tsm - TypeScript Module Loader
redux - A JS library for predictable global state management