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

url-state-sync

v0.0.2

Published

Minimal URL ⇄ state sync store — framework-agnostic, zero-dependency.

Readme

url-state-sync

Minimal, type-safe URL ⇄ state sync store — framework-agnostic, zero-dependency.

A tiny store that keeps your state in memory and syncs it to the URL query — you decide when it writes, and values keep their declared types.

Install

pnpm add url-state-sync

Usage

import { createURLStore } from 'url-state-sync'

const store = createURLStore({
  keyword: '',
  page: 1,
  tags: [] as string[],
})

store.getState()             // { keyword, page, tags } — snapshot, safe to destructure
store.get('page')            // read one field
store.set({ keyword: 'x' })  // mutate memory only (or auto-sync with { immediate: true })
store.sync()                 // manually write state → URL (replaceState)
store.reset()                // back to defaults + write URL

const off = store.subscribe(s => render(s)) // notified on set / reset / back-forward
off()                        // unsubscribe

Type-safe by schema

initialState doubles as a type schema — each field is decoded from the URL back to the type of its default:

const store = createURLStore({
  accountId: '',        // string  → stays a string
  amount: 0,            // number  → Number()
  active: false,        // boolean → 'true' / 'false'
  tags: [] as string[], // array   → multi-value (?tags=a&tags=b)
})

That's the whole reason a schema exists: long numeric strings keep their precision. A snowflake ID like 2069365971128094722 declared as accountId: '' stays exactly that string — it is never coerced to a Number (which would round it to …094700). Only declared fields are read; unknown query params are ignored.

Options

createURLStore(initial, {
  immediate: true,       // write the URL on every set (default false — manual sync)
  listenPopState: false, // stop re-reading on back/forward (default true)
})
  • Manual sync — by default set only touches memory; call sync() when you actually want the address updated (e.g. on a "Search" click). No history spam while typing.
  • Destructure freely — every method is a closure; getState() is a function, so there's no stale-snapshot trap.
  • Back / forwardpopstate re-reads state from the URL by default.

Roadmap

  • v1 — minimal manual store
  • v2 — schema-based typing (snowflake-safe) + array / multi-value params
  • v3subscribe for reactive UIs (notified on any state change)
  • later — pluggable adapters (vue-router, hash routing…), Vue composables

License

MIT