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

@technical-1/workers

v1.1.1

Published

Web/Service Worker awareness for Puppeteer pages: enumerate workers, evaluate inside a worker, and observe worker lifecycle with typed events and a DI logger.

Readme

@technical-1/workers

Web/Service Worker awareness for Puppeteer pages: enumerate workers, evaluate inside a worker, and observe worker lifecycle with typed events and a DI logger.

Convenience wrapper. This package wraps puppeteer-core's page.workers(), WebWorker.evaluate, and the workercreated/workerdestroyed events with typed lifecycle events, typed errors (WorkerError), and a DI logger. It adds no capability beyond those primitives — it exists so worker enumeration, in-worker evaluation, and lifecycle tracking compose through one consistent, typed surface instead of three ad hoc call sites.

import { listWorkers, evaluateInWorker, observeWorkers } from "@technical-1/workers";

// Snapshot the page's currently-live workers:
const workers = listWorkers(page);
console.log(workers.map((w) => w.url));

// Run code inside a worker's realm:
const result = await evaluateInWorker(workers[0].worker, () => self.location.href);

// Track workers spawning/exiting for the page's lifetime:
const observer = observeWorkers(page, {
  onWorkerCreated: (info) => console.log("created", info.url),
  onWorkerDestroyed: (info) => console.log("destroyed", info.url),
  onError: (err) => console.error(err.message),
});

// ... run your flow ...

console.log(observer.created); // readonly WorkerInfo[] currently live
console.log(observer.events);  // readonly WorkerLifecycleEvent[] full history
observer.dispose();            // detach both listeners (idempotent)

Errors

Evaluate failures (e.g. the worker was destroyed mid-evaluate, or the function threw) and consumer-callback failures inside observeWorkers are surfaced as WorkerError from @technical-1/core, discriminated by err.name === "WorkerError", with retryable:true. evaluateInWorker throws it directly; observeWorkers routes it to the onError callback and the injected logger at level error — never thrown from inside the event listener.

v1 limitations

  • listWorkers returns a snapshot, not a live view — it does not update as workers spawn/exit (use observeWorkers for lifecycle tracking).
  • observeWorkers attaches its own workercreated/workerdestroyed listener pair; multiple concurrent observers on one page all fire (puppeteer allows multiple listeners), so attach one.

Peer

Requires puppeteer-core >=22 <25. It is a type-only peer dependency — it supplies the Page/WebWorker types used at compile time; this package never imports it at runtime.