Recipes

Status: Stable (guidance)
Package: @jayoncode/storage

Previous: Composition · Next: Best practices

Copy-paste patterns. Prefer these over inventing helpers Storage intentionally rejects (e.g. a collections API).

How to use this page

Level	Do this
Beginner	Copy Preferences or Short-lived cache, change namespace, ship
Intermediate	Use List under one key / SSR-safe patterns
Advanced	Combine with Maintenance / Snapshots in app code
:::

Preferences (long TTL)

import { createStorage, createLocalStorageAdapter } from "@jayoncode/storage";

const prefs = createStorage({
  namespace: "app-prefs",
  adapter: createLocalStorageAdapter(),
  policies: {
    preferences: { ttl: { days: 365 } },
  },
});

prefs.set("theme", "dark", { policy: "preferences" });

Short-lived cache

const cache = createStorage({
  namespace: "app-cache",
  adapter: createLocalStorageAdapter(),
  policies: {
    cache: { ttl: { minutes: 15 } },
  },
});

cache.set("feed", data, { policy: "cache" });

List under one key (no collections API)

Store an array value; mutate in the app. Storage stays a persistence layer.

type Todo = { id: string; title: string };

const storage = createStorage<Todo[]>({
  namespace: "app",
  adapter: createLocalStorageAdapter(),
});

function addTodo(todo: Todo): void {
  const list = storage.get("todos") ?? [];
  storage.set("todos", [...list, todo]);
}

Multi-key update with rollback

import { transaction } from "@jayoncode/storage/transactions";

transaction(storage, () => {
  storage.set("profile", profile);
  storage.set("profile:meta", { savedAt: Date.now() });
});

Sweep expired entries

import { cleanup } from "@jayoncode/storage/maintenance";

cleanup(storage, { removeInvalid: true });

Form drafts

Form Intelligence owns draft UX. Storage may hold opaque blobs later — do not rebuild draft UX here.

See also: Overview · Core · Transactions