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

hapiest-kue

v0.0.3

Published

Simple wrapper for Kue that hooks it up with node-config and provides logical separation between job creation and job processing

Downloads

8

Readme

Purpose

hapiest-kue provides a light-weight wrapper around kue designed with engineering best practices in mind. You must explicitly request permission to create jobs or process jobs separately (as opposed to having direct access to Queue which lets you do both). It works with Node config out of the box giving you flexibility to configure your Redis connection. It only returns a job after it's successfully created and uses a Promise interface using Bluebird Promise implementation.

Setup

  1. Install Docker! https://docs.docker.com/engine/installation/

  2. Build the docker image

npm run docker:build

  1. If you're using an IDE, I recommend setting NODE_CONFIG_DIR to src/config.

  2. If you want to run tests on your local machine instead of Docker, you should create src/config/default.json with Redis connection locally:

{
  "queue": {
    "redis": {
      "host": "192.168.99.100",
      "port": "6379",
      "db": 5
    }
  }
}
  1. Run docker-compose up

Running tests

The official tests should be run using npm test