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

@adrienlcp/safe-storage

v0.1.1

Published

localStorage that never throws: every read, write and removal returns a Result, and typed reads check what they find

Downloads

495

Readme

@adrienlcp/safe-storage

localStorage that never throws. Every read, write and removal returns a Result, and a typed read checks what it finds instead of trusting it.

localStorage throws on plain access in a Safari private window, when the user blocks site data, when the quota is full, and on a server, where it does not exist. An app that calls it bare turns any of those into a blank page.

pnpm add @adrienlcp/safe-storage

Reading

import { readRecognizedText, readStoredJson, readStoredText } from '@adrienlcp/safe-storage'

readStoredText('app:volume')
// Result<string | null, 'unavailable'>

readRecognizedText({ isRecognized: isLocale, key: 'app:locale' })
// Result<Locale | null, 'unavailable' | 'unrecognized'>

readStoredJson({ isValue: isTrainingLog, key: 'app:log' })
// Result<TrainingLog | null, 'unavailable' | 'unrecognized'>
  • A null success is nothing stored yet, never a failure.
  • 'unavailable' — localStorage threw, or there is none.
  • 'unrecognized' — something is stored, but the guard refuses it: a value an older version wrote, text that is not JSON, JSON of another shape.

The guard is a plain type predicate, so no schema library is required. One plugs in through its own:

const isTrainingLog = (value: unknown): value is TrainingLog =>
  trainingLogSchema.safeParse(value).success

Writing and removing

import { removeStored, writeStoredJson, writeStoredText } from '@adrienlcp/safe-storage'

writeStoredText({ key: 'app:locale', text: 'fr' })  // Result<void, 'unavailable' | 'quota'>
writeStoredJson({ key: 'app:log', value: log })     // Result<void, 'unavailable' | 'quota'>
removeStored('app:locale')                          // Result<void, 'unavailable'>

'quota' is a full storage. A value JSON.stringify cannot write, like a cycle, still throws: that is a bug in the caller, not a refusal.

What to do with a failure

This package reports; it never decides. What the user gets instead is the app's call, made where the storage is read:

const readTrainingLogOrEmpty = (): TrainingLog => {
  const stored = readStoredJson({ isValue: isTrainingLog, key: LOG_KEY })

  return stored.status === 'success' ? (stored.data ?? EMPTY_LOG) : EMPTY_LOG
}