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

@alt-stack/workers-trigger

v1.6.0

Published

Trigger.dev integration for @alt-stack/workers-core

Readme

@alt-stack/workers-trigger

Trigger.dev SDK v3 server adapter for @alt-stack/workers-core. It re-exports the core API, so one package can define job routers and turn them into Trigger.dev task definitions.

Requirements

  • Node.js 18+
  • Trigger.dev SDK 3.x and a configured Trigger.dev project
  • Zod 4
pnpm add @alt-stack/workers-trigger @trigger.dev/sdk zod

Usage

import { createWorker, init, ok } from "@alt-stack/workers-trigger";
import { z } from "zod";

const { router, procedure } = init<{ mailer: Mailer }>();

const jobs = router({
  "send-welcome-email": procedure
    .input({ payload: z.object({ email: z.string().email() }) })
    .task(async ({ input, ctx }) => {
      await ctx.mailer.send(input.email);
      return ok();
    }),
});

export const { tasks } = createWorker(jobs, {
  createContext: () => ({ mailer }),
  onError: (error, ctx) => console.error(ctx.jobName, error),
});

export const sendWelcomeEmail = tasks["send-welcome-email"];

Export task entries from a source path Trigger.dev discovers. Tasks with payload schemas use schemaTask; tasks without them use task; cron procedures use schedules.task. Queue names and cron timezones are not currently forwarded.

Returned Altstack Err values do not fail a Trigger.dev run; throw to enter onError and provider failure handling. Optional telemetry creates OpenTelemetry spans when the API is installed/configured.

Documentation

License

MIT