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 🙏

© 2025 – Pkg Stats / Ryan Hefner

sails-hook-rabbitmq-worker

v0.0.6

Published

hook for easy configuration of rabbitmq workers

Readme

sails-hook-rabbitmq-worker

sails hook for easy rabbitmq worker integration

This is in beta, still working out connection error handling

Jobs are defined in api/jobs. They should look like this:

// api/jobs/testJob.js
module.exports = {
    name: 'testJob', // required
    worker(msg) { // required
        console.log('worker args', msg.content.toString())
        console.log('msg.ack', msg.ack)
        return Promise.resolve()
    },
    durable: true, // optional, defaults to true
    prefetch: 3 // optional, defaults to 1
}

A config file is also required, it should look something like this (given values are defaults unless otherwise noted):

var path = require('path')

module.exports.rabbitworker = {
  options: {
    runJobs: true, // optional flag for whether this particular instance should consume jobs from the queue
    exchangeName: 'some_exchange_name',  // optional, defaults to 'sails_jobs'
    retryFailedJobs: true, // optional flag for if jobs should be retried (one additional time) if they fail
    heartbeat: 5, // optional number of seconds, defaults to no heartbeat
    retryConnectionAttempts: 3, // optional number of retry attempts for initial connection
    retryConnectionTimeout: 10000, // optional number of milliseconds before attempting to retry after a connection error
    retryDroppedConnectionAttempts: 100, // optional number of retry attempts after a dropped connection 
    host: 'localhost', // all of these connection settings are optional.  if omitted, these are the defaults.
    port: 5672,
    username: 'guest',
    password: 'guest',
    ssl: false
  },
  jobs: require('require-all')(path.join(__dirname, '../api/jobs'))  // required
}

Note the peer dependency on require-all.

Once this is set up, you can create a new job like this:

sails.createJob('nameOfTheJob', 'string message')