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/test

v1.0.6

Published

EveryState Test: Testing library with TDD-style assertions and event-sequence tracking

Readme

@everystate/test v1.0.5

Testing library for EveryState with TDD-style assertions

Zero-dependency testing library for EveryState. Assert on state changes, event sequences, and types.

Installation

npm install @everystate/test @everystate/core

Quick Start

import { createEventTest, runTests } from '@everystate/test';

const results = runTests({
  'counter increments': () => {
    const t = createEventTest({ count: 0 });
    t.trigger('count', 1);
    t.assertPath('count', 1);
    t.trigger('count', 2);
    t.assertPath('count', 2);
  },

  'type assertions': () => {
    const t = createEventTest({ name: 'Alice', age: 30 });
    t.assertType('name', 'string');
    t.assertType('age', 'number');
  },
});

if (results.failed > 0) process.exit(1);

API

  • createEventTest(initialState) - Create a test instance with an EveryState store
    • .trigger(path, value) - Set a value at a path
    • .assertPath(path, expected) - Assert exact value at a path
    • .assertType(path, type) - Assert type of value at a path
    • .assertShape(path, shape) - Assert object shape at a path
    • .assertArrayOf(path, elementShape) - Assert array with element shape
    • .assertArrayLength(path, length) - Assert array length
    • .assertEventFired(path, times) - Assert event fired N times
    • .getEventLog() - Get the full event log
    • .getTypeAssertions() - Get recorded type assertions
  • test(name, fn) - Run a single test, returns true/false
  • runTests(tests) - Run a map of tests, returns { passed, failed }

Features

  • Zero dependencies - No external test framework needed
  • TDD-style assertions - assertPath, assertType, assertShape, etc.
  • Event sequence testing - Track order of state changes
  • Type extraction - Infer types from state for type generation
  • Fast - 100 tests in ~0.5ms

Documentation

Full documentation available at everystate.dev.

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 | 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/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 EveryState stores. Zero dependency. | MIT | | @everystate/types | Typed dot-path autocomplete for EveryState stores | MIT | | @everystate/view | State-driven view: DOMless resolve + surgical DOM projector. View tree as first-class state | MIT | | @everystate/vue | Vue 3 composables adapter: provideStore, usePath, useIntent, useWildcard, useAsync | MIT |

Self-test (CLI, opt-in)

The self-test verifies the exported API surface (createEventTest, test, runTests) and exercises the test runner itself. It does not require @everystate/core - it only checks that functions exist with the right types and arities, and that test() and runTests() produce correct pass/fail results.

It is opt-in and never runs automatically on install:

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

# if installed locally
everystate-test-self-test

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

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

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

License

MIT (c) Ajdin Imsirovic