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

@usedetach/cli

v0.2.1

Published

Detach CLI — link a storefront, push component manifests, generate types, run the local dev loop.

Readme

@usedetach/cli

The cms command for Detach storefronts.

npm install -D @usedetach/cli
cms login              # device flow; token stored in ~/.config/detach/credentials.json
cms init               # idempotent setup: config, .env.local, types, manifest registration
cms components push    # register this build's component manifest with an environment
cms content validate   # CI gate: does the environment's published content still render?
cms dev                # attach to a running dev server and expose it as an editor preview target
cms types generate     # typed content reads from the registered manifest

cms init is the path to run — and to re-run — when a storefront misbehaves; it never overwrites and reports every step. --check changes nothing.

In CI, CMS_CI_KEY / CMS_MANAGEMENT_KEY take precedence over stored credentials, so builds stay deterministic. cms content validate exits 1 on errors (a placed component the build no longer defines, a valued field removed or retyped), --strict also fails on warnings, and --json is for machines.