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

@grupo-gcb/nestjs-sqs

v1.0.1

Published

<p align="center"> <a href="http://nestjs.com/" target="blank"> <img src="https://nestjs.com/img/logo-small.svg" width="120" alt="Nest Logo" /> </a> <a href="https://github.com/@grupo-gcb/nestjs-sqs" target="blank"> <h1 align="center">@grupo

Downloads

2

Readme

Fork by: @nestjs-packages/sqs

Description

nestjs-sqs is a project to make SQS easier to use and control some required flows with NestJS. This module provides decorator-based message handling suited for simple use.

This library internally uses bbc/sqs-producer and bbc/sqs-consumer

Installation

$ npm i --save grupo-gcb/nestjs-sqs
# or
$ yarn add grupo-gcb/nestjs-sqs

Quick Start

SqsModule

forRootAsync

For use SqsModule, You have to set SQS configurations. you can set SQS configurations by forRootAsync method. after forRootAsync method called, every sqs produers and consumers use SQS configurations returned by forRootAsync useFactory method

@Module({
  imports: [
    SqsModule.forRootAsync({
      imports: [ConfigModule],
      useFactory: (configService) => {
        const config = {
          region: configSerivce.region, // us-east-1
          endpoint: configSerivce.endpoint, // https://sqs.us-east-1.amazonaws.com
          accountNumber: configSerivce.accountNumber, // 000000000000
          credentials: {
            accessKeyId: configSerivce.accessKeyId,
            secretAccessKey: configService.secretAccessKey,
          },
        };
        return SqsConfig(config);
      },
      injects: [ConfigSerivce],
    }),
  ],
})
class AppModule {}

registerQueue

Second you have to register queues. register queues means create sqs-producer and sqs-consumer by queueOptions that passed into registerQueue parameter default type of queueOption is 'ALL'

SqsModule.registerQueue(
  {
    name: 'queueName',
    type?: SqsQueueType.Consumer // 'ALL'|'CONSUMER'|'PRODUCER'
    consumerOptions?: {},
    producerOptions?: {}
  },
  ...
);

consume message

You need to decorate providers and methods in your NestJS providers in order to have them be automatically attached as message(event) handlers for incoming SQS messages

@SqsProcess(/** name: */ queueName)
export class AppMessageHandler {
  @SqsMessageHandler(/** batch: */ false)
  public async handleMessage(message: AWS.SQS.Message) {}

  @SqsConsumerEventHandler(/** eventName: */ SqsConsumerEvent.PROCESSING_ERROR)
  public onProcessingError(error: Error, message: AWS.SQS.Message) {
    // report errors here
  }
}

You need to pass queueName to SqsProcess decorator. unless SqsModule won't register Consumer. One class can only handle one queue. so if you want to enroll dead letter queue, you have to make new class that handle dead letter queue

Produce messages

SqsService needs to be injected to produce the message.

export class AppService {
  public constructor(
    private readonly sqsService: SqsService,
  ) { }

  public async dispatchSomething() {
    await this.sqsService.send<BodyType>(/** name: */ 'queueName', {
      id: 'id',
      body: { ... },
      groupId: 'groupId',
      deduplicationId: 'deduplicationId',
      messageAttributes: { ... },
      delaySeconds: 0,
    });
  }
}

Configuration

See here, and note that we have same configuration as bbc/sqs-consumer's. In most time you just need to specify both name and queueUrl at the minimum requirements.

License

This project is licensed under the terms of the MIT license.