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

ssr-safe-storage

v0.1.0

Published

A typed localStorage wrapper that falls back to an in-memory store outside the browser, so the same calls work during server-side rendering.

Readme

ssr-safe-storage

A typed localStorage wrapper that keeps working outside the browser.

Values are serialised as JSON going in and parsed coming out, so you store objects rather than strings. During server-side rendering — or in a test runner without a DOM — the same calls fall through to an in-memory store instead of throwing on a missing localStorage.

import { getInStorage, setInStorage, removeInStorage } from "ssr-safe-storage"

setInStorage("preferences", { theme: "dark", density: "compact" })

const preferences = getInStorage<{ theme: string }>("preferences")
// → { theme: "dark", density: "compact" }

removeInStorage("preferences")

Installation

pnpm add ssr-safe-storage

No dependencies.

API

| Function | Purpose | | --- | --- | | getInStorage<T>(key) | Reads and parses a value | | setInStorage(key, data) | Serialises and writes a value | | removeInStorage(key) | Removes a key |

getInStorage distinguishes two empty cases: it returns null when the key was never set, and undefined when the value stored for it was itself undefined. That distinction matters when absence and "explicitly nothing" mean different things to the caller.

The in-memory fallback

Outside the browser, reads and writes go to a plain object living for the duration of the process. It is not shared between requests and it is not a server-side persistence layer — it exists so the calling code can stay identical on both sides instead of being wrapped in typeof window checks.

Development

pnpm install
pnpm test
pnpm typecheck
pnpm lint
pnpm build

License

MIT