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

@affenity/simplebull

v0.0.1

Published

A highly opinionated, highly simplistic, highly not recommended for anyone else to use, library that looks like inngest.com and trigger.dev, but is free, straightforward to use, and are built on top of existing tools.

Readme

SimpleBull

A highly opinionated, highly simplistic, highly not recommended for anyone else to use, library that looks like inngest.com and trigger.dev, but is free, straightforward to use, and are built on top of existing tools.

(Also meaning it's simple as heck to self-host. Just use Redis and BullMQ).

This is meant more like a proof oc concept, and not a production ready library.

Installing

bun add simplebull

Usage

//> Declaring an "Action" (Queue & Worker)
const processVideo = SimpleBull.action(
    {
        slug: "process-video",
        schema: z.object({
            videoUrl: z.string()
        })
    },
    {
        jobs: {
            retries: {
                max: 3,
                delay: 1000,
                backoff: "fixed"
            }
        }
    },
    async ({ ctx, job, runner, data }) => {
        const downloadVideo = await runner.step(
            { id: "download-video" },
            () => downloadVideoFromUrl(data.videoUrl)
        );

        const transcodeVideo = await runner.step(
            { id: "transcode-video" },
            () => transcodeVideo(downloadVideo)
        );

        const generateTranscripts = await runner.step(
            { id: "generate-transcripts" },
            () => generateTranscripts(transcodeVideo)
        );

        const writeToDb = await runner.step(
            { id: "write-to-db" },
            () => db.video.create({
                downloadedId: downloadVideo.id,
                transcriptsLocation: generateTranscripts.location,
                transcodedVideoLocation: transcodeVideo.location
            })
        );

        return {
            dbId: writeToDb.id
        };
    }
);

//> Initiating
const client = SimpleBull.client({ redisUrl: "redis://" });
await client.init(); //> This prepared the bullmq queues and workers
await client.start(); //> This starts them for work

//> Adding a job
processVideo.addJob({
    videoUrl: "https://www.youtube.com/watch?v=dQw4w9WgXcQ"
});

As you can see, each step is run redundantly, and if any step fails, the previous successful steps won't be run again, and the job will start from the failed step.