nanostores
create-figma-plugin
nanostores | create-figma-plugin | |
---|---|---|
17 | 1 | |
4,772 | 860 | |
2.6% | - | |
8.4 | 9.0 | |
1 day ago | 28 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.
create-figma-plugin
-
Using tsm as a shebang interpreter in TypeScript
create-figma-plugin: a comprehensive toolkit for developing plugins and widgets for Figma and FigJam. It is written in TypeScript and uses tsm for its development process
What are some alternatives?
jotai - 👻 Primitive and flexible state management for React
design-tokens - 🎨 Figma plugin to export design tokens to json in an amazon style dictionary compatible format.
effector-react - Business logic with ease ☄️
html-figma - Builder.io for Figma: AI generation, export to code, import from web
nanoid - A tiny (124 bytes), secure, URL-friendly, unique string ID generator for JavaScript
tinyhttp - 🦄 0-legacy, tiny & fast web framework as a replacement of Express
zustand - 🐻 Bear necessities for state management in React
tsm - TypeScript Module Loader
nextjs-course-code - Source code for my NextJS course (https://acad.link/nextjs)
figma-plugin-ds - A small lightweight design system for use in Figma Plugins
SWR - React Hooks for Data Fetching
stylo - A new Design-as-code language side project.