npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@everystate/core

v1.2.1

Published

EveryState: Lightweight event-driven state management with path-based subscriptions, wildcards, and async support

Downloads

108

Readme

@everystate/core v1.2.1

EveryState: Observable state management with dot-path addressing

Every piece of state has a name. Every name is subscribable. Every operation is visible.

Installation

npm install @everystate/core

Zero external dependencies - Pure state management with no third-party packages required.

Quick Start

import { createEveryState } from '@everystate/core';

const store = createEveryState({ count: 0, user: { name: 'Alice' } });

// Subscribe to specific path
const unsub = store.subscribe('count', (value) => {
  console.log('Count changed:', value);
});

// Update state
store.set('count', 1);

// Get state
const count = store.get('count');

// Wildcard subscription
store.subscribe('user.*', ({ path, value }) => {
  console.log(`User field ${path} changed to:`, value);
});

// Check if a path exists (handles intentional undefined)
store.has('count');        // true
store.has('nonexistent');  // false

// List all leaf paths under a prefix
store.keys('user');        // ['user.name']
store.keys();              // ['count', 'user.name']

// Cleanup
unsub();

Self-test (CLI, opt-in)

Run the bundled zero-dependency self-test locally to verify core behavior. It is opt-in and never runs automatically on install:

# via npx (no install needed)
npx everystate-self-test

# if installed locally
everystate-self-test

# or directly
node node_modules/@everystate/core/self-test.js

You can also run the npm script from the package folder:

npm --prefix node_modules/@everystate/core run self-test

Integration tests (@everystate/test)

The tests/ folder contains a separate integration suite that uses @everystate/test (declared as devDependency). This is an intentional tradeoff: the self-test stays lightweight, while integration tests remain available for deeper validation.

For end users (after installing the package):

# Install test dependency
npm install @everystate/test

# Run from package folder
cd node_modules/@everystate/core
npm run test:integration
# or short alias
npm run test:i

Or, from your project root:

npm --prefix node_modules/@everystate/core run test:integration
# or short alias
npm --prefix node_modules/@everystate/core run test:i

For package developers (working in the source repo):

# Install dev dependencies first
npm install

# Run integration tests
npm run test:integration

What is EveryState?

EveryState is a reactive state management library where:

  • Every value lives at a named dot-path (like user.profile.name)
  • Every path is subscribable with wildcards (user.*)
  • Every change is observable and traceable
  • No magic, no proxies, no hidden dependency tracking

Core Features

  • Path-based subscriptions: Subscribe to exactly what you need
  • Wildcard support: user.* catches all user changes
  • Atomic batching: Multiple writes, single notification per path
  • Path introspection: has() and keys() for runtime path discovery
  • Zero dependencies: ~2KB minified
  • Framework-agnostic: Works with React, Vue, Angular, Solid, Svelte, or vanilla JS

Why EveryState?

State management shouldn't be a black box. You should be able to:

  • Ask "which paths changed most often?"
  • See "how long did that update take?"
  • Know "which component is listening to this path?"

EveryState makes state addressable, observable, and testable without special tooling.

Ecosystem

| Package | Description | License | |---|---|---| | @everystate/aliases | Ergonomic single-character and short-name DOM aliases for vanilla JS | MIT | | @everystate/angular | Angular adapter: usePath, useIntent, useWildcard, useAsync - bridges store to Angular signals | MIT | | @everystate/core | Path-based state management with wildcard subscriptions and async support. Core state engine (you are here). | MIT | | @everystate/css | Reactive CSSOM engine: design tokens, typed validation, WCAG enforcement, all via path-based state | MIT | | @everystate/examples | Example applications and patterns | MIT | | @everystate/pattern-catalogue | Comprehensive demonstration of 13 UI patterns using the "No Ceiling" hybrid architecture | MIT | | @everystate/perf | Performance monitoring overlay | MIT | | @everystate/react | React hooks adapter: usePath, useIntent, useAsync hooks and EventStateProvider | MIT | | @everystate/renderer | Direct-binding reactive renderer: bind-*, set, each attributes. Zero build step | MIT | | @everystate/router | SPA routing as state | MIT | | @everystate/solid | Solid adapter: usePath, useIntent, useWildcard, useAsync - bridges store to Solid signals | MIT | | @everystate/test | Event-sequence testing for UIstate stores. Zero dependency. | MIT | | @everystate/types | Typed dot-path autocomplete for EveryState stores (you are here) | MIT | | @everystate/ui | Tree-shakable, transparent, framework-free imperative UI components. Every component is readable vanilla JS | MIT | | @everystate/view | State-driven view: DOMless resolve + surgical DOM projector. View tree as first-class state | MIT | | @everystate/view-ui | Declarative UI component specs: plain JS objects + handler maps. The declarative twin of @everystate/ui | MIT | | @everystate/vue | Vue 3 composables adapter: provideStore, usePath, useIntent, useWildcard, useAsync | MIT |

Documentation

Full documentation available at everystate.dev.

Source code: https://github.com/ImsirovicAjdin/everystate-core

License

MIT © Ajdin Imsirovic

|