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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@torthu/jacketui-store

v0.7.0

Published

Simple Store implementation

Readme

JacketUI Store

Store based on thinking from compassionate components.

Installation

Requires Typescript.

npm i --save @torthu/jacketui-store

Philosophy

We want flexibility in our components and escape hatches in order to solve edge cases and make components truly expandable and reusable.

In order to achieve this we need to create flexible components, meaning expandable and full of escape hatches in order to cater for edge cases.

Features

The Store is based on the Flux-architecture/ELM-architecture with one twist: it supports asynchronous action handlers in addition to the usual synchronous reducer functions.

Anti-features: Not synchronous, not pure. Features: Async is first-class member, not an afterthought or delegated to another library.

This means that the store is not synchronous, meaning it does not comform to f(state, action) => state, but rather f(state, action) => [multiple states over time].

Action handlers

An action handler is essentially the same as a reducer in e.g useReducer. It is a function that takes the existing state and an action and returns a new state.

When setting up the store, you pass an array of action handlers, please note that the order is important since earlier action handlers will impact the state passed to later action handlers.

Reducers - synchronous action handlers

A reducer is a synchronous function that takes a state, and action and returns a new state: (state, action) => state.

This is the same concept, and same function signature, as in useReducer.

Combine Reducers

If you have multiple reducers, you can combine them into one using the combineReducers function:

const combinedReducer = combineReducers(reducer1, reducer2, reducer3);

Effects - asynchronous action handlers

Effects are asynchronous functions that can be used to perform side effects, such as fetching data from an API.

Effects are designed to solve side effects such as data fetching, file saving, or any other work that is not necessarily expected to return a new state.

Their function signature is designed to be dissimilar to the Reducers in order to easily differentiate them:

const effect: Effect<State, Action> = async ({getState, setState, dispatch, action}) => {}

Selectors - retrieves a View from the state

A selector is a function that takes the state and returns a view (subset or manipulated version) of the state.

Slices - a View and its update callback

A slice is a view of the state, and a callback that is called when the view changes.

Debugging and dev tools

The store can be connected to the Redux DevTools extension.

In a React context, simply use the provided hook:

const [state, dispatch, store] = useStore(actionHandlerArray, initialState);
useDevtools(store, {name: "My Store Name"})

In other contexts you can use the connectDevtools function:

const store = new Store({ initialState, actionHandlers });

// Remember to disconnect at the end of the lifecycle of the store
const disconnect = connectDevtools(store, {name: "My Store Name"});

Usage

See examples/example.ts for example usage.

If you are using React, you can use the included useStore hook instead: const [state, dispatch, store] = useStore(actionHandlerArray, initialState);

Architecture

Data Flow