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

@blit-sh/bin

v0.35.0

Published

Installs the prebuilt blit binary for your platform; default export is the binary path.

Readme

@blit-sh/bin

The blit binary, distributed via npm. Installing @blit-sh/bin pulls in exactly one prebuilt package for your platform (@blit-sh/bin-<os>-<cpu>[-musl]) through optional dependencies — nothing else.

CLI

npm i -g @blit-sh/bin
blit open

Bundle the binary in your own tool

The default export is the absolute filesystem path to the blit executable, so you can spawn it directly. Resolution happens on import and throws with an actionable message if the matching prebuilt package was not installed.

ESM

import blit from "@blit-sh/bin";
import { spawn } from "node:child_process";

spawn(blit, ["open"], { stdio: "inherit" });

CommonJS

const blit = require("@blit-sh/bin");
const { spawn } = require("node:child_process");

spawn(blit, ["open"], { stdio: "inherit" });

Helpers

Lower-level resolution helpers are available on the @blit-sh/bin/resolve subpath (and as named exports of the main entry):

import {
  binaryPath,
  binaryName,
  candidatePackages,
  isMusl,
} from "@blit-sh/bin";
// or: import { binaryPath } from "@blit-sh/bin/resolve";

| export | description | | --------------------- | ------------------------------------------------------- | | default | absolute path to the blit binary (resolved at import) | | binaryPath() | same path, computed lazily; throws if unavailable | | binaryName() | "blit" or "blit.exe" | | candidatePackages() | platform package names, in resolution order | | isMusl() | true on musl-libc Linux |

Platforms

Linux x64/arm64 (glibc & musl), macOS arm64, Windows x64 — matching the binaries the blit release pipeline builds.

License

MIT