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

localit

v6.1.0

Published

Manage your Storage with ease, adding expiration dates through a simple API

Readme

localit

minzip size dependency count tree-shakeable

🔥 A lightweight, fully-typed wrapper around the Web Storage API (localStorage / sessionStorage) with expiration support, optional key namespacing, and change event listeners.

✅ Features

  • Store/retrieve plain and complex values easily, no JSON.stringify required.
  • Expiration time support, you decide how log to cache the data
  • Family-based key namespacing
  • Listen to changes on individual keys
  • No dependencies, <1kB gzipped

📦 Install

npm i localit
# or
yarn add localit
# or
pnpm add localit

🚀 Usage

Import

import { localit } from "localit";

set(key, value, config?)

Store a value in storage.

localit.set("foo", { bar: 42 }, { expiration: "5m" });
localit.set("name", "User123", { family: "user" });
localit.set("list", new Set([1, 2, 3]), { type: sessionStorage });
const tomorrow = new Date();
tomorrow.setDate(tomorrow.getDate() + 1);
localit.set("lasts-a-day", { some: "data" }, { expiration: tomorrow });

Config options:

  • type: localStorage (default) or sessionStorage
  • family: string to namespace the key (stored as family::key)
  • expiration: "Xs", "Xm", "Xh", or "Xd". Also accepts a Date object for a fixed expiration date.

get(key, config?)

Retrieve a value.

const value = localit.get("foo");
const set = localit.get<Set<number>>("list");

If the value has expired, it will be removed and null is returned.


remove(key, config?)

Delete a specific key.

localit.remove("foo");

Also, specify a family for even more control

localit.set('foo', 'bar') // Will be stored with 'foo' as key
localit.set('foo', 'baz' { family: 'bar' }) // Will be stores with 'bar::foo key

localit.remove('foo') // Will detele 'foo' but not 'bar::foo'

clearFamily(family, storage?)

Remove all keys that belong to a given family.

localit.clearFamily("user");
localit.clearFamily("cache", sessionStorage); // Only delete `cache` family in sessionStorage, localStorage keys are kept intact

bust(storage?)

Clear all keys from the given storage (localStorage by default)

localit.bust(); // clears localStorage
localit.bust(sessionStorage); // clears sessionStorage

on(key, callback)

Subscribe to key changes (e.g. via set() or remove()).

localit.on("foo", (newValue) => {
  console.log("foo changed:", newValue);
});

Note: this is not the same as the native storage event—it only triggers within the current context when localit methods are used.


🧪 Example

localit.set("cart", { count: 3 }, { expiration: "2h" });

const cart = localit.get("cart"); // { count: 3 }

localit.on("cart", (val) => {
  console.log("Cart updated:", val);
});

localit.set("cart", { count: 4 }); // logs: Cart updated: { count: 4 }

📚 Types

type ExpirationType =
  | `${number}s`
  | `${number}m`
  | `${number}h`
  | `${number}d`
  | Date;

type LocalitSetConfig = {
  type?: Storage;
  family?: string;
  expiration?: ExpirationType;
};

type LocalitGetConfig = {
  type?: Storage;
  family?: string;
};

🛠 Author

Alejandro Mayol
github.com/alexmayol