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

sqs-json

v1.1.0

Published

Simplifies reception, processing, and removal of JSON objects stored in SQS

Downloads

37

Readme

sqs-json

npm version CircleCI

Simplifies reception, processing, and removal of JSON objects stored in SQS.

npm install sqs-json

API

sqsJson.processJsonMessages(sqs, params, callback<message>) -> Promise

  1. Polls a queue using provided sqs and params: sqs.receiveMessage(params)
  2. Attempts to parse each message as JSON
  3. If the message is a valid JSON, calls the provided callback
  4. If the callback resolves for the given message, removes the message from the queue, otherwise leaves the message in the queue
  5. Outputs the total number of messages, number of succeeded (resolved by callback), failed (rejected by callback OR invalid JSON messages), and an array of results for each message in the format defined below

Note: unless Raw Message Delivery is enabled for the queue subscription, the parsed message will also include AWS wrappers. You may want to enable this in your AWS console to work with pure JSON objects easier.

Example:

const
  AWS = require('aws-sdk'),
  sqsJson = require('sqs-json'),
  sqs = new AWS.SQS({ apiVersion: '2012-11-05' });

...

return sqsJson.processJsonMessages(sqs, {
  QueueUrl: 'https://sqs.us-east-1.amazonaws.com/12345678912/my-awesome-queue',
  MaxNumberOfMessages: 10,
  VisibilityTimeout: 30
}, (message) => {
  if (iWantThisMessage(message)) {
    return Promise.resolve({
      mySuccessfulResult: 'myValue'
    })
  } else {
    return Promise.reject('no!')
  }
});

Example response:

{
  "total": 3,
  "succeeded": 2,
  "failed": 1,
  "results": [
    {
      "isError": false,
      "result": {
        "mySuccessfulResult": "myValue"
      }
    },
    {
      "isError": true,
      "result": "no"
    },
    {
      "isError": true,
      "result": {
        "name": "MessageValidationError",
        "details": {
          "error": "SyntaxError: Unexpected token N in JSON at position 0",
          "rawMessage": {
            "MessageId": "900efefe-0342-4573-8920-fb24c3a8ce19",
            "ReceiptHandle": "AQEBA5...",
            "MD5OfBody": "8677b7d6bed5e6948ab6e232889940d5",
            "Body": "NotAJson"
          }
        }
      }
    }
  ]
}

In the example, the message corresponding to the first result will be removed from the queue as it was successful, while the remaining two will be rejected and stay in the queue adhering to SQS "maximum receives" policies.