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

@nori-zk/workers

v0.0.4

Published

An abstraction to enable workers which operate on node and the browser.

Downloads

22

Readme

Workers

A library to enable creating and using workers within a browser and Node.js context.

Define a worker

// Simulate long import time due to top level async
await new Promise((res) => setTimeout(res, 10000));

export class EchoWorker {
    private id: string;
    constructor(id: string) {
        this.id = id;
    }

    async echo(req: { msg: string }): Promise<{ echoed: string }> {
        return { echoed: `Echo: ${req.msg}${this.id}` };
    }

    async shout(req: { msg: string }): Promise<{ upper: string }> {
        return { upper: req.msg.toUpperCase() };
    }
}

1. Use Node.js workers

Only valid in a Node.js environment (e.g., backend services, CLI tools)

  • You must lift the pure worker class into an actual worker.

    // workers/echo/node/parent.ts
    import { WorkerParent } from '@nori-zk/workers/node/parent';
    import { type EchoWorker } from 'path/to/echo/worker';
    import { createProxy } from '@nori-zk/workers';
    
    const workerUrl = new URL('./child.js', import.meta.url);
    
    export const EchoWorkerParent = createProxy<typeof EchoWorker>(
        new WorkerParent(workerUrl)
    );
    // workers/echo/node/child.ts
    import { EchoWorker } from 'path/to/echo/worker';
    import { WorkerChild } from '@nori-zk/workers/node/child';
    import { createWorker } from '@nori-zk/workers';
    
    createWorker(new WorkerChild(), EchoWorker);

    Usage in a Node.js app:

    import { EchoWorkerParent } from './node/parent.js';
    
    async function main() {
        // Construct parent with arguments
        const echoWorker = new EchoWorkerParent('node-app');
    
        // Optional: wait for ready (all calls are buffered)
        await echoWorker.ready;
    
        // Call worker methods
        const echoed = await echoWorker.echo({ msg: 'hello' });
        console.log(echoed); // { echoed: 'Echo: hellonode-app' }
    
        const upper = await echoWorker.shout({ msg: 'hello' });
        console.log(upper); // { upper: 'HELLO' }
    
        // Clean up
        echoWorker.signalTerminate();
    }
    
    main();

2. For browsers

Use this if you're building your own worker pipeline for the browser.

  • You must lift the pure worker class into an actual worker.

    // workers/echo/browser/parent.ts
    import { WorkerParent } from '@nori-zk/workers/browser/parent';
    import { type EchoWorker } from 'path/to/echo/worker';
    import { createProxy } from '@nori-zk/workers';
    
    const worker = new Worker(new URL('./child.js', import.meta.url), {
        type: 'module',
    });
    
    const workerParent = new WorkerParent(worker);
    
    export const EchoWorkerParent = createProxy<typeof EchoWorker>(workerParent);
    // workers/echo/browser/child.ts
    import { EchoWorker } from 'path/to/echo/worker';
    import { WorkerChild } from '@nori-zk/workers/browser/child';
    import { createWorker } from '@nori-zk/workers';
    
    createWorker(new WorkerChild(), EchoWorker);

    Usage in a browser app:

    import { EchoWorkerParent } from './browser/parent.js';
    
    async function runBrowserCode() {
        // Construct parent with arguments
        const echoWorker = new EchoWorkerParent('browser-app');
    
        // Optional: await ready
        await echoWorker.ready;
    
        // Calls are automatically buffered if the worker isn't ready yet
        const echoed = await echoWorker.echo({ msg: 'hi' });
        console.log(echoed); // { echoed: 'Echo: hibrowser-app' }
    
        const upper = await echoWorker.shout({ msg: 'hi' });
        console.log(upper); // { upper: 'HI' }
    
        // Terminate when done
        echoWorker.signalTerminate();
    }
    
    runBrowserCode();

3. Buffering & ready behavior

  • Internally, the parent uses deferred promises:

    async call<Res>(methodName: string, ...args: any[]): Promise<Res> {
        if (methodName === 'worker-construct') {
            // Wait for child to spawn
            await this.workerSpawnedDeferred.promise;
        } else {
            // Wait for worker readiness
            await this.workerReadyDeferred.promise;
        }
        // Forward call to worker
        // ...
        return deferred.promise;
    }
  • All method calls are queued automatically until the worker is ready.

  • await ready is optional; you can call methods immediately after construction.

  • Construction arguments depend on the worker class definition; only provide them if the constructor requires them.