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 🙏

© 2025 – Pkg Stats / Ryan Hefner

graphile-worker-tasks

v2.0.0

Published

Organize and collect graphile-worker tasks

Readme

graphile-worker-tasks

A utility for organizing and collecting graphile-worker tasks.

This library is particularly useful when working with graphile-worker in environments where the built-in file-based auto-discovery mechanism is either not possible or not desirable, such as when using bundlers or other specialized setups.

Install

pnpm add graphile-worker-tasks

Use

Define tasks:

import { defineTask } from "graphile-worker-tasks"

export default defineTask("sendEmail", async (email: string) => {
  console.log(`Sending email: ${email}`)
})

You can organize tasks across as many modules as needed.

Once defined, collect and run your tasks:

import { run } from "graphile-worker"
import { createTaskList, mergeTasks } from "graphile-worker-tasks"

import sendEmailTask from "../tasks/sendEmail"

const tasks = mergeTasks([
  sendEmailTask,
  // ...
])

await run({
  connectionString: "...",
  taskList: createTaskList(tasks),
  parsedCronItems: [],
})

Extend GraphileWorker.Tasks to ensure the graphile-worker tooling picks up the types:

declare global {
  namespace GraphileWorker {
    interface Tasks extends GraphileWorkerTasks<typeof tasks> {}
  }
}

There is no magic in this module — basically, it just stores the original task names and handles the typing quirks.

You can omit the helpers and use the task handlers directly, but make sure to use the correct names:

import { run } from "graphile-worker"

// Import the module under a name that matches the queue job name.
import sendEmail from "../tasks/sendEmail"

await run({
  connectionString: "...",
  taskList: {
    sendEmail, // The key here must match the queue job name.
    // ...
  },
  parsedCronItems: [],
})