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

@turndb/cli-darwin-arm64

v0.2.0

Published

turndb command-line binary for darwin-arm64

Readme

@turndb/cli

The turndb command line: inspect, verify, query, and ship a store from a terminal with no server running.

npm install -g @turndb/cli
turndb --version                                # the crate version compiled in
turndb import  mystore.turndb traces.jsonl      # each line needs a "body"; other scalars become attributes
turndb inspect mystore.turndb                   # manifest, parts, fold, members, retained revisions
turndb verify  mystore.turndb --deep            # every record, piece, frame, and pin
turndb query   mystore.turndb "SELECT model, count(*) FROM t GROUP BY model"
turndb backup  mystore.turndb snap.turndb       # the current store authority as one self-contained store
turndb query   snap.turndb "SELECT count(*) FROM t"

turndb help prints the authoritative verb set; where it and this list disagree, it is right.

What ships

A native binary, delivered through a per-platform package that npm installs as an optional dependency and skips everywhere it does not apply. There is deliberately no WASM fallback: the binary needs positioned reads and an OS-enforced writer lock. In-place content-punch and free-space-punch use Linux hole punching or Windows sparse-range zeroing and report unsupported on other platforms, so a platform without a build says so rather than silently running a different engine with different guarantees.

Published slices: linux-x64-gnu, linux-arm64-gnu, darwin-x64, darwin-arm64, and win32-x64-msvc. Other targets must build from source with cargo install turndb.

Reading a store the library wrote

Every read verb accepts a current-draft .turndb store file. A store written by the turndb wasm package or @turndb/native reads here identically. Any other physical identity is refused. There is no converter, migration reader, or fallback parser for discarded draft layouts.

Operating verbs (compact for part merge, refold, content-punch, free-space-punch, erase, recover for manifest promotion, reclaim, and backup) take the writer role — flock on Unix or LockFileEx on Windows, on the store container handle — and close it when they finish, so a store they have operated on is exactly one file.

Apache-2.0. See LICENSE and NOTICE.