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

@lapismd/jj-history

v0.1.0

Published

Lossless typed clients for host-admitted operation-pinned JJ history

Readme

@lapismd/jj-history

A headless typed client for operation-pinned history from tauri-plugin-jj-store. The native host admits the vault, source paths, private cache and caller window. The client only receives the resulting opaque vault scope and handles.

import { tauriHistory } from "@lapismd/jj-history/tauri";
import { invoke } from "@tauri-apps/api/core";

const history = tauriHistory(admittedVaultToken, invoke);
const heads = await history.heads();
const handle = await history.open(heads.heads[0]);
try {
  const status = await history.status(handle);
  // Wait through the application's own lifecycle while status is preparing.
  if (status.state === "ready") {
    const result = await history.read(handle, { kind: "query_info" });
  }
} finally {
  await history.close(handle);
}

Use HistoryClient from the main entry with an injected HistoryTransport for other text transports. Neither entry imports Tauri or chooses native policy. Errors propagate without retries; applications own cancellation and closure. Retain failed close handles until the native host confirms their release.

Call history.blame(handle, { commit, path, continuation: null }) for recorded line attribution. Retain returned progress and its opaque continuation until complete; every page uses the handle's original operation and admission.

Types and runtime validation derive from the native Rust schema. Integer values within JavaScript's safe range decode as numbers; larger values decode as bigint. Supply large input integers as bigint, never rounded numbers. Request and reply envelopes are bounded UTF-8 JSON text, version 1. Do not parse their inner payloads with ordinary JSON.parse.

See the local repository manual for host admission, operation pins and platform qualification. Source and archive checks do not establish a released package or qualify a downstream application.