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

stored-state

v1.0.2

Published

Simplest persistent state for browser apps

Readme

stored-state

npm version license

Simplest persistent state for browser apps

  • State cached in memory and synced to localStorage
  • Fast reads and state survive reloads
  • Zero setup, zero dependencies
import { state } from "stored-state";
state.user = { name: "peter" };
state.token = "1234";
state.theme = "dark";

Install

npm install stored-state

Update State

Update state by assignment. Values can be any primitives, objects or arrays. Always assign top level keys, not nested fields.

import { state } from "stored-state";
state.theme = "dark";
state.layout = {
	lastViewed: "analytics"...
};

// NOT do
state.user.lastViewed = ... 

Read state

Read state like a normal object. State can be accessed and modified anywhere in your app.

import { state } from "stored-state";

console.log(state);
if (state.theme === "dark") ...

Clear State

Clear single value. Two options:

delete state.theme;
state.theme = null;

Clear whole state

state.clear();

Advantages

  • Simple: state.name = value
  • Fast: values cached in memory after first access
  • Small: ~750 bytes min+gzip
  • Zero setup, zero dependencies

License

MIT

Hint

If you don't want manually import { state } from "stored-state" many times,
you can just add this import at app start.

import "stored-state/global"

// Now you can access STATE anywhere in your app without imports

STATE.user = {...}