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 🙏

© 2024 – Pkg Stats / Ryan Hefner

@flatfile/queue

v1.1.0

Published

## Engines - Sync - BullMQ

Downloads

4

Readme

@flatfile/queue

This library provides a full-service queue abstraction layer for all systems in Flatfile. It provides a queue agnostic approach that allows us flexibility on the queue engine and effective testing.

Roadmap

  • [ ] Add support for a Redis Queue
  • [ ] Add callback methods to the worker for job failure, timeout, etc.
  • [ ] Verify behavior of SIGINT / SIGTERM on graceful shutdown
  • [ ] Ensure consistent queue depth alerting

Drivers

SyncDriver

This will execute jobs immediately. This is very helpful for testing job logic, as it does not require testing the internal operations of a specific queue engine.

GraphileDriver({ databaseUrl })

This provides a powerful Postgres backed queue implementation with ms latency.

BullMQDriver (coming soon)

Add support for a redis-based BullMQ implementation

Writing a new Worker

import { Worker } from '@flatfile/queue'
import { Injectable } from '@nestjs/common'

@Injectable() // -> optional if using in Nest
export class MyWorker extends Worker<{ myProp: string }> {
  /**
   * Provide a custom worker name, otherwise will use class name
   * @default MyWorker
   */
  workerName = 'custom-name'

  /**
   * Determine the execution priority of this job, lowe numbers are higher priority
   * @default 50
   */
  priority = 1

  /**
   * Delay the execution of this job by a number of ms
   * @default 0
   */
  delay = 0

  /**
   * Set a number of milliseconds from enqueue where this job should be expired
   * If the job is delayed unintentionally beyond this point it will be discarded
   * @default 0
   */
  expiration = 0

  /**
   * Provide a set of retry options for this job
   * @default 6
   */
  maxAttempts = 3

  execute({ myProp }, attempt) {
    // write logic here
  }
}

Triggering a Job in Nest

When you're ready to send a new job, you just need to call addJob(worker, params, overrides) and the magic will happen. If you're using SyncProvider it will execute immediately, otherwise it'll execute as soon as the queue reaches that job.

@Injectable()
class MyService {
  constructor(
    private queueProvider: QueueProvider,
    private myWorker: MyWorker
  ) {}

  async myMethod() {
    // enqueue something (await because maybe it'll happen synchronously)
    await this.queueProvider.queue.addJob(
      this.myWorker,
      { myProp },
      { delay: 500 }
    )
  }
}

Implementing a Nest Worker Job

import { NestFactory } from '@nestjs/core'
import { QueueProvider } from '@flatfile/queue'
import { AppModule } from './App.module'

async function bootstrap() {
  const app = await NestFactory.createApplicationContext(AppModule)
  const { queue, workers } = app.get(QueueProvider)

  await queue.runWorkers(...workers)
}
bootstrap()
ts-node ./worker.ts

Implementing a Filtered Nest Worker

async function bootstrap() {
  const app = await NestFactory.createApplicationContext(AppModule)
  const { queue, workers } = app.get(QueueProvider)

  // provider.workers magically detects any Workers exported from any module
  // use a filter function to run specific workers on a give node
  await queue.runWorkers(
    ...workers.filter((w) => process.argv.includes(w.name))
  )
}
bootstrap()
ts-node ./worker.ts hard-job other-job