Storeon

Storeon — 335-byte Redux-like state manager with event-driven API.

App UtilsSimple

Stack Components

LibraryStoreon 3.x

Why

Tiny, modular via plugins, Redux-like but simpler, async actions built-in. 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 minimal Redux-like state. Avoid for complex derived state.

How

1. npm install storeon 2. Create store with modules 3. useStoreon in React 4. Dispatch events 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 { createStoreon } from 'storeon'; const store = createStoreon([module]); store.dispatch('increment');

Common Problems

⚠No devtools — use storeon/devtools
⚠Type safety — use @storeon/typescript
⚠Configuration drift between environments — use infrastructure-as-code (Terraform/Pulumi) to keep dev/staging/prod identical

Best Practices

✓Use modules for separation
✓Keep events as string constants
✓Set up health checks and graceful shutdown — handle SIGTERM to drain in-flight requests before exit

FAQ

What is Storeon and what projects is it for?

Storeon — 335-byte Redux-like state manager with event-driven API. 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 Storeon in 10 minutes?

Two steps: (1) npm install storeon; (2) Create store with modules. 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 Storeon and how do I avoid it?

The most common pitfall is: No devtools — use storeon/devtools. 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 Storeon?

Best practices for Storeon include: Use modules for separation; Keep events as string constants; Set up health checks and graceful shutdown — handle SIGTERM to drain in-flight requests before exit. The first one — "Use modules for separation" — should be set up at project init to avoid costly rework later.

When should I NOT choose Storeon?

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). Storeon shines for mid-to-high complexity full-stack and API work — don't over-engineer simple static pages with it.