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

typedstash

v0.1.3

Published

Typed JSON store with zod schema validation and numeric per-store migrations

Readme

typedstash

Typed JSON storage for app config, CLI state, and small local data stores.

typedstash writes one JSON file, validates data with zod, and migrates data with per-store numeric versions. It is a new package API, not a compatibility layer for conf.

Install

bun add typedstash zod

Schema

import Store from 'typedstash';
import {z} from 'zod';

const store = new Store({
	projectName: 'my-app',
	schema: z.object({
		volume: z.number().min(0).max(100).default(50),
		endpoint: z.string().url().optional(),
	}),
});

store.get('volume');
//=> 50

store.set('volume', 101);
//=> Error: Config schema violation

Zod required fields without .default() or .optional() must already exist in the config file, otherwise the initial load fails with a schema violation.

Migrations

schemas.length is the current data-format version. migrations[i] transforms data from version i + 1 to i + 2.

import Store from 'typedstash';
import {z} from 'zod';

const v1 = z.object({
	name: z.string(),
});

const v2 = z.object({
	name: z.string().default(''),
	count: z.number().default(0),
});

const store = new Store({
	projectName: 'my-app',
	schemas: [v1, v2] as const,
	migrations: [
		data => ({...data, count: 0}),
	],
});

store.get('count');
//=> 0

Each migration is a pure function. typedstash validates each result with the target zod schema and writes a checkpoint only after that step succeeds.

Reserved Field

__version at the top level of the config file is reserved and managed by typedstash. Do not use it in your zod schema or public writes.

__internal__ has no special meaning in typedstash and is treated as normal user data.

Tests

bun test
bun run test:e2e
bun run typecheck
bun run build
bun run publish:check

bun run test:e2e builds the package and imports typedstash through the package export, so it catches packaging/export issues that source-level tests cannot. bun run publish:check builds the package and runs publint --pack bun against the files that would be published.

License

MIT. Includes code derived from sindresorhus/conf; see LICENSE.