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

hub-runner

v0.2.3

Published

Runs a hub workspace's Mac bots on this Mac under launchd, with no app needed.

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Maintainers

rcontirconti

Keywords

Readme

hub-runner

Runs a hub workspace's Mac bots on this Mac. It runs under launchd, so no app has to be open.

npm i -g hub-runner --min-release-age=0
hub-runner login
hub-runner start

login signs in with Vercel, asks which workspace this Mac runs bots for, and stores a session of the runner's own in ~/.hub/local/credentials.json. The Vercel token is revoked once the hub has the session.

| Command | What it does | |---|---| | hub-runner start [--take-over] | Starts the runner under launchd (~/Library/LaunchAgents/dev.hub.runner.plist). It starts again at every login and is not restarted after a crash: run start again. --take-over claims the Mac slot from another Mac. | | hub-runner stop | Stops it. | | hub-runner restart | Lets the open turns finish, then starts it again. | | hub-runner status | The runner's state, pid, version, bots, and whether launchd has it loaded. Exits 1 when it isn't running. | | hub-runner logs [-f] | The log, ~/.hub/local/runner.log. | | hub-runner logout | Stops it and deletes the stored session. |

Update

npm i -g hub-runner@latest --min-release-age=0 && hub-runner restart

restart lets the turns open now finish, so no bot is cut off.

--min-release-age=0 lets the newest release install when your npm config holds packages back for a few days (min-release-age). It applies to this one install, and hub-runner has no dependencies, so nothing else skips the wait.

Notes

  • Node 24 or later, and pnpm on your PATH when you run start: the runner uses both to set the bots up.
  • The hub is https://hosted-hub.playground-vercel.tools; set HUB_URL when you run login for another one.
  • The HubHosted app only shows the runner's state. Quitting, signing out of or replacing the app doesn't touch the runner.
  • If the runner doesn't start, hub-runner status and hub-runner logs say why.