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 🙏

© 2025 – Pkg Stats / Ryan Hefner

sharedstorage

v0.8.0

Published

Proposal for a Shared Storage API

Readme

SharedStorage

A proposed API for shared storage in the browser along with a working polyfill (and browser settings emulator).

Example usage

(async () => {
let status, attempt, data;

({status, attempt, data} = await SharedStorage.set({
  namespace: 'test', data: 'abc'
}));
assert(
  status === 'success' && attempt === 'set' && data === undefined,
  'Passed setting'
);

({status, attempt, data} = await SharedStorage.get({namespace: 'test'}));
assert(
  status === 'success' && attempt === 'get' && data === 'abc',
  'Passed getting'
);

// Stop-gap utility until polyfill can farm out data to other of its
//  domains and/or browsers can determine any quotas
const {maxRemaining} = await SharedStorage.getMaxRemaining();
assert(typeof maxRemaining === 'number');
})();

Use cases

  • Operating on same files with different viewers/editors (e.g., word processing documents, SVG editors, etc.)
  • Decentralized, offlineable social media
  • Email, chat, and feed subscription systems
  • Hierarchical pseudo-file system available to websites
  • Plugin architecture for any web app (sites can use shared storage to save their plugin URLs while the main app uses postMessage to communicate with those apps)
  • Web Intents replacement (see "Plugin architecture" just above)

To-dos

  1. Preferences page currently only shows preferences as set by other sites; make editable
  2. Get origin-specific namespacing types working:
  3. origin -> namespace (written by single origin but read-only to others) - E.g., for .gov practicing Open Data
  4. namespace -> origins (written by each origin and read-only to others) - E.g., sites enumerating their details for a shared namespace (could be chaotic if versioned/interpreted differently, however). Useful, e.g., for delivery of emails
  5. origin -> namespace -> origins (main area written by single origin, but other origins being allowed to add to namespaces; read-only to others) - E.g., for plugins to a particular site (e.g., handling sites of .gov data)
  6. Consider key, removeItem, clear, length; renaming get/set to getItem/setItem
  7. Implement shared IndexedDB version