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

@watashino/scheduler

v0.0.1

Published

A powerful and flexible job scheduling library for NestJS applications, built on top of BullMQ

Downloads

34

Readme

Scheduler Library

A powerful and flexible job scheduling library for NestJS applications, built on top of BullMQ.

Overview

The Scheduler Library provides a simple way to define and manage scheduled jobs in your NestJS application. It uses BullMQ under the hood for reliable job processing and scheduling.

Key features:

  • Declarative job definition using decorators
  • Automatic discovery of jobs and handlers
  • Support for recurring jobs with flexible scheduling options
  • Type-safe job data

Installation

npm install @watashino/scheduler

Basic Usage

1. Define a Scheduler Job

Create a class that extends SchedulerJob and decorate it with @Scheduler():

import { Scheduler } from '@watashino/scheduler';
import { SchedulerJob } from '@watashino/scheduler';

@Scheduler()
export class YourJob extends SchedulerJob {
  // Define a unique key for this job
  static readonly key = 'your-job-key';

  // Define when the job should repeat
  repeat = {
    every: 1000 * 60 * 60, // Run every hour
  };

  // Optional: Define job template data
  template = {
    data: {
      // Your job data here
    },
  };
}

2. Create a Job Handler

In a service, create a method decorated with @OnSchedule() to handle the job:

import { Injectable, Logger } from '@nestjs/common';
import { OnSchedule } from '@watashino/scheduler';
import { YourJob } from './your.job';

@Injectable()
export class YourService {
  private readonly logger = new Logger(YourService.name);

  @OnSchedule(YourJob.key)
  async handleYourJob(data: Record<string, unknown>) {
    this.logger.log(`Processing job with data: ${JSON.stringify(data)}`);
    // Your job handling logic here
  }
}

3. Register Your Job

Make sure both your job class and service are provided in your module:

import { Module } from '@nestjs/common';
import { SchedulerModule } from '@watashino/scheduler';
import { YourJob } from './your.job';
import { YourService } from './your.service';

@Module({
  imports: [SchedulerModule.forRoot()],
  providers: [YourJob, YourService],
})
export class YourModule {}

Documentation

For more detailed documentation, including advanced usage, configuration options, and API reference, please see the full documentation.