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

@redocly/replay

v0.24.0

Published

The Replay app uses different database backends depending on the platform: - **Tauri (desktop)**: SQLite with Drizzle ORM - **Web**: IndexedDB with the `idb` library

Readme

Replay

Database Migrations

The Replay app uses different database backends depending on the platform:

  • Tauri (desktop): SQLite with Drizzle ORM
  • Web: IndexedDB with the idb library

SQLite Migrations (Tauri)

SQLite schema is defined in src/db/schema/ using Drizzle ORM. Migrations are auto-generated.

To add a migration:

  1. Update the schema in src/db/schema/ (e.g., history.schema.ts)
  2. Generate the migration from the apps/replay-app directory:
    pnpm db:generate
  3. This creates a new .sql file in apps/replay-app/src-tauri/migrations/ with a unique name
  4. Migrations run automatically on app startup via the Rust backend
  5. Alternatively, manually create a new migration file in apps/replay-app/src-tauri/migrations/:
# Format: YYYYMMDDHHMMSS_description.sql
src-tauri/migrations/20241224120000_add_user_settings.sql
-- Add new table
CREATE TABLE IF NOT EXISTS user_settings (
    id TEXT PRIMARY KEY NOT NULL,
    key TEXT NOT NULL UNIQUE,
    value TEXT NOT NULL
);

IndexedDB Migrations (Web)

IndexedDB uses version-based migrations.

To add a migration:

  1. Increment the version constant in the storage class (e.g., HISTORY_DB_VERSION in HistoryIndexedDBStorage.ts)
  2. Update the setupDatabase() method to handle both initial creation and upgrades:
const HISTORY_DB_VERSION = 2; // Increment for new migration

private static setupDatabase(db: IDBPDatabase<unknown>): void {
  // Initial setup (runs for new databases)
  if (!db.objectStoreNames.contains('history')) {
    const store = db.createObjectStore('history', { keyPath: 'id' });
    store.createIndex('by-date', 'date');
  }

  // Version 2: Add new index (runs on upgrade from v1)
  const tx = db.transaction('history', 'readwrite');
  const store = tx.objectStore('history');
  if (!store.indexNames.contains('by-new-field')) {
    store.createIndex('by-new-field', 'newField');
  }
}

Best practices:

  • Always check if stores/indexes exist before creating
  • Keep schema definitions in sync between SQLite and IndexedDB
  • Test migrations with existing data before release