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

background-process-js

v6.3.4

Published

A set of util tools for create background process.

Downloads

1,489

Readme

background-process-js

A set of util tools for create background process.

How to use?

You have two manners for use background-process-js, you can use some our implementations or you can create your own.

Using our implementation.

  import { SQSClient } from 'aws-sdk';
  import { SQSConsumer, SQSConfig, ConsumerConfig } from 'background-process-js';

  const sqs = new SQSClient();
  const sqsConfig = {
    client: sqs,
    WaitTimeSeconds: 20,
    VisibilityTimeout: 30,
    MaxNumberOfMessages: 10,
    mainQueueUrl: 'https://sqs.{region}.amazonaws.com/{accountID}/{queueName}'
    deadQueueUrl: 'https://sqs.{region}.amazonaws.com/{accountID}/{queueName}'
  };


  // If it is true will continuously polling in the queue,
  // and if the queue return less than MaxNumberOfMessages and greather than zero
  // will set a timeout with WaitTimeSeconds number for continuously polling queue.  
  
  // If it is false you must control the timeouts and times for polling.
  const continuouslyPolling = true || false;
                                              // Default false
  const consumer = new SQSConsumer(sqsConfig, continuouslyPolling);

Using your own implementation.

  import { Message } from 'aws-sdk';
  import { Consumer } from "background-process-js";

  export class SQSConsumer extends Consumer<Message> {
    
    constructor() {
      super({
        hasDeadQueue: true || false,
        maxReceivedMessages: 10,
        continuouslyPolling: true || false,
        timeoutAfterEndingPollingInMilliseconds: 20 * 1000, // 20 seconds
      });
    }

    protected async getMessages(): Promise<Message[]> {
      // code...
    }

    protected async deleteMessages(messages: Message[]): Promise<void> {
      // code...
    }

    protected async markAsDeadMessages(messages: Message[]): Promise<void> {
      // code...
    }
  }

For any implementation you can set the following listeners and methods.

  // This process event will be execute by default every 1 minute 
  consumer.process(({ messages, scalingId }) => {
    // code for processing message...

    const deadMessages = [...messages];
    const processedMessages = [...messages];

    if (isInvalidMessage) {
      // This emitter will be log an error and stop consumer
      consumer.catch(new Error());
    }

    // This emmiter will be delete message from queue
    consumer.finish(scalingId, processedMessages);

    // This emmiter will be send messages to dead queue
    consumer.dead(scalingId, deadMessages);
  });

  // This method will start many pollings
  consumer.poll(5);