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

@suli-g/stratum

v0.2.0

Published

A layered React framework for building multi-system management applications.

Readme

Stratum

A layered React framework for building multi-system management applications.
Define the architecture once. Generate every new system with one command.

Setup

npm install
npm run dev

Testing

yarn test          # run unit test suite
yarn test:watch    # run tests in watch mode

Generator

npm run make:system <name>

Scaffolds a complete management system and wires it into the app automatically.

Examples

npm run make:system orders
npm run make:system staff
npm run make:system delivery-zone   # hyphenated → camelCase/PascalCase

Each run creates three files and patches three registries:

| Created | Purpose | |---|---| | src/model/<name>.js | Type definition + factory function | | src/store/slices/<name>.js | Reducer + action type constants | | src/views/<Name>/index.jsx | View component wired to the store |

| Patched | What changes | |---|---| | src/store/reducer.js | Import + delegation line added | | src/store/initialState.js | Slice key added | | src/views/tabs.js | Import + registry entry added |

The tab is live in the nav immediately. No other files change.

Individual commands

npm run make:model  <name>   # model file only
npm run make:slice  <name>   # slice file only
npm run make:view   <name>   # view folder only

Architecture

src/
├── util/          Pure functions. No React, no state.
├── model/         Data shapes and factory functions.
├── store/         useReducer + Context. All app state lives here.
│   └── slices/    One file per system. Generated by make:system.
└── views/         UI only. Reads store, dispatches actions.
    └── shared/    Primitive components (Btn, Field, EmptyState…)

Dependency rule — imports flow downward only:

views → store → model → util

No layer may import from a layer above it.