Nanostores

Nanostores — tiny (286 bytes) state manager for any framework.

App UtilsSimple

Stack Components

Librarynanostores 0.x

Why

Framework-agnostic, tree-shakeable, perfect for micro-frontends and edge. Utility libraries (lodash, date-fns, zod) save 100s of hours of boilerplate.

Zod reached 5M weekly npm downloads in 2024 as runtime validation became essential with TypeScript-first APIs.

When

Use for tiny cross-framework state. Avoid for complex derived state.

How

1. npm install nanostores 2. Create atom 3. Subscribe/use in framework 4. Update store 5. Add environment configuration — cp .env.example .env && edit values 6. Run tests — npm test or pnpm test to verify setup 7. Deploy — git push to trigger CI/CD or manual deploy

Example

import { atom } from 'nanostores'; export const count = atom(0); count.set(count.get() + 1);

Common Problems

⚠No devtools — use @nanostores/logger
⚠Re-render optimization — use useStore in React
⚠Configuration drift between environments — use infrastructure-as-code (Terraform/Pulumi) to keep dev/staging/prod identical

Best Practices

✓Use computed() for derived state
✓Keep stores small and focused
✓Set up health checks and graceful shutdown — handle SIGTERM to drain in-flight requests before exit

FAQ

What is Nanostores and what projects is it for?

Nanostores — tiny (286 bytes) state manager for any framework. It pairs layered technologies for end-to-end type safety and out-of-the-box deploys, fitting everything from MVPs to production SaaS.

How do I spin up a working demo with Nanostores in 10 minutes?

Two steps: (1) npm install nanostores; (2) Create atom. Get the local dev server running, then wire one real data source to verify the end-to-end loop.

What is the most common pitfall with Nanostores and how do I avoid it?

The most common pitfall is: No devtools — use @nanostores/logger. Avoid it by adding the matching checklist to your PR template and running type-check + lint + unit tests in CI — three gates before merge.

What are the best practices for Nanostores?

Best practices for Nanostores include: Use computed() for derived state; Keep stores small and focused; Set up health checks and graceful shutdown — handle SIGTERM to drain in-flight requests before exit. The first one — "Use computed() for derived state" — should be set up at project init to avoid costly rework later.

When should I NOT choose Nanostores?

Pick something else in three cases: (1) the team has zero experience with the core framework and the deadline is tight (learning-curve risk); (2) it's a pure content/marketing site (Astro is lighter); (3) you need very high throughput (>10k RPS) or strict-consistency microservices (Go/Rust). Nanostores shines for mid-to-high complexity full-stack and API work — don't over-engineer simple static pages with it.