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

@adpharm/bit

v0.1.7

Published

A lightweight CLI for pulling shared files from a bit-compatible host directly into your project.

Readme

@adpharm/bit

A lightweight CLI for pulling shared files from a bit-compatible host directly into your project.

Installation

npm install -g @adpharm/bit
# or
bunx @adpharm/bit@latest import ...

Usage

bit import <slug> --host <url> --to <path>
bit status <slug> --host <url> --path <file>

bit import

Pull a file from the registry into your project.

| | Description | |---|---| | <slug> | The file's unique slug — <project>/<file> (as shown in the web app) | | --host <url> | Base URL of the host (e.g. https://yourapp.com) | | --to <path> | Output destination — a file path or a directory |

--to behaviour

| Value | Result | |---|---| | ./src/components/ | Writes to ./src/components/<filename> using the file's original name | | ./src/components/MyButton.tsx | Writes directly to that path |

Examples

# Write to a directory — filename comes from the registry
bit import my-project/ui-button --host https://yourapp.com --to ./src/components/

# Write to an explicit file path
bit import my-project/ui-button --host https://yourapp.com --to ./src/components/Button.tsx

bit status

Check whether your local copy of a file is in sync with the registry. Prints a coloured unified diff if it differs, or a confirmation message if it matches. Exits 1 when out of sync (useful in CI).

| | Description | |---|---| | <slug> | The file's unique slug — <project>/<file> (as shown in the web app) | | --host <url> | Base URL of the host (e.g. https://yourapp.com) | | --path <file\|dir> | Local file or directory to compare against the registry | | --check | Silent mode — no output, just exit 0 (in sync) or 1 (out of sync) |

--path behaviour

| Value | Resolves to | |---|---| | ./src/components/ | ./src/components/<filename> using the file's original name | | ./src/components/MyButton.tsx | That exact path |

Examples

# Compare by directory — filename comes from the registry
bit status my-project/ui-button --host https://yourapp.com --path ./src/components/

# Compare an explicit file path
bit status my-project/ui-button --host https://yourapp.com --path ./src/components/Button.tsx

# Silent check — useful for programmatic/typechecker use
bit status my-project/ui-button --host https://yourapp.com --path ./src/components/ --check

API

The CLI expects the host to expose:

GET /api/bit/:projectSlug/:fileSlug

Response shape:

{
  "name": "Button.tsx",
  "slug": "my-project/ui-button",
  "content": "..."
}

Returns 404 if the slug doesn't exist, 429 if rate-limited.