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

@projectpac/worker

v0.6.0

Published

Part of PAC: @projectpac/worker.

Readme

@projectpac/worker

The process that spawns models. It is a cordis app of its own, not a thread of the daemon's: a model is heavy, holds handles, and may not come back, and the daemon has to keep answering while one runs.

It keeps a folder of its own under the node's data directory, defaultWorker/ by default, holding its row file executors.yml and one folder per executor row for whatever that executor writes. It never opens the node's store. It asks the daemon's control api for work -- claim, renew, settle -- naming the executor rows it carries, and is handed the oldest pending turn for one of them. Every claim is also its sign of life.

Four rules it keeps:

  • It pulls. Nothing tells it a turn is waiting; it asks, once a second when idle. The only latency a turn pays is that interval.
  • The executor decides whether a payload is runnable. A payload the executor refuses fails the turn as invalid-payload before anything is spawned. The worker reads neither payload.
  • It decides nothing about what a turn means. It hands the executor's text back exactly as produced, and the loop on the daemon's side tells the caller.
  • A turn it claimed is always answered. A settle whose reply was lost is retried, and the api takes the repeat; a lease it can no longer renew is given up, and the model stopped, because the daemon has already failed the turn without it.

Shutdown is bounded: claiming stops, turns in flight are asked to stop and then made to, and whatever was still running when the process went is failed by its lapsed lease on the daemon's side.