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 🙏

© 2026 – Pkg Stats / Ryan Hefner

aws-sqs-poller

v0.2.0

Published

Polling aws simple queue messages.

Readme

aws-sqs-poller

A simple sqs message poller.

What it does ?

It provides the functionality to call receiveMessage() on AWS::SQS after short interval of time and put them in internal messages list and emit them one by one, when internal messages list is empty it pulls messages again from SQS and so on. Idea is to pull next messages batch only when we are done processing the previous one. This can help scaling certain areas of your app that are using same message queue.

Events

- message

Sample Code

var Poller  = require('aws-sqs-poller'),
    options = {
        name            : "your-queue",             // required
        useIAMRole      : true                      // optional
        accessKeyId     : 'aws-key',                // required if useIAMRole = false 
        secretAccessKey : 'aws-secret-access-key',  // required if useIAMRole = false
        region          : 'us-west-1',              // optional, default is 'us-east-1'
        maxMessages     : 4,                        // optional, default is 10, must be between 1-10 
    };

var myQueue = new Poller(options);

myQueue.start();                        // calling this will start the poller
myQueue.on('message', function (msg) {  // will emitted on first message or on calling mqQueue.next()
    
    console.log('handle: ', msg.receiptHandle);
    console.log('data: ', msg.body); // internally will try parese it as JSON
    console.log('md5: ', msg.md5OfBody); 
    
    /*
    * Your business logix
    */
      
    // Want to delete message from SQS.
    msg.remove();
                           
    // Move to next message
    myQueue.next();                     
});

Change List

0.2.0

  • Bumped version. Added log process.pid as log prefix

0.1.8 - 0.1.12

  • code refactoring

0.1.7

  • log message change

0.1.6

  • bug fix

0.1.4

  • bug fix, unable to pull message in some cases.

0.1.0

  • not to start poller if there is problem talking to Queue.

0.0.9

  • README changes

0.0.8

  • new option.useIAMRole for production use
  • Upgrade packages
  • Removed incomplete test cases and unwanted packages, package is much leaner now