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

@chadsly/knit

v0.1.5

Published

Install and run the local Knit daemon, then connect Knit Browser Composer from the Chrome Web Store or a local unpacked extension.

Readme

@chadsly/knit

@chadsly/knit installs the host-specific Knit daemon from bundled release artifacts and exposes it through the knit command.

Install:

npm install -g @chadsly/knit

Start Knit:

knit start

Install the browser extension after the daemon is running:

  • Chrome Web Store: Knit Browser Composer
  • Local unpacked install: open chrome://extensions, enable Developer mode, click Load unpacked, and select extension/chromium from the Knit repository

Pair it from the Knit UI with Capture, review, and send -> Chrome Extension.

Other commands:

  • knit path
  • knit version

What happens on install:

  • postinstall selects the archive for the current OS and CPU
  • verifies it against the bundled release manifest
  • extracts the native daemon into the package runtime directory

Supported platforms:

  • macOS: x64, arm64
  • Linux: x64, arm64
  • Windows: x64

When you run knit start, the native daemon prints the local UI URL, the Chrome Web Store link, the local unpacked extension path, and the pairing path in the Knit UI. This package still only installs the daemon/runtime; the browser extension is installed separately.