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

@pcs/prospect-queueworkerbase

v1.0.2

Published

Base implementation of the worker processes

Downloads

5

Readme

@pcs/prospect-queueworkerbase

Base implementation of the worker processes


Usage:

Create a node module that requires sk-worker.

This should contain a class that extends SkWorker and optionally overrides any of the listed functions.

Each override should receive the job and resolve a promise to the job:

beforeJob(job)

This is called when a job is picked from the queue to be processed. Any changes to be made to the job before it is processed should be made here.

processJob(job)

This is called to actually process a job. The functionality that the job needs to achieve should be here.

afterJob(job)

This is called after a job is processed, regardless of whether it succeeds or fails. Any clean up required following the processing of a job should be here.

completeJob(job)

This is called after a job is completed successfully.

erroredJob(job)

This is called after a job errors.


Processing Jobs

processJobs should be called on the worker, passing the queue name to process, the details of the redis server hosting the queue and the log level at which to output.

Example app.js

const config = require('./config/local.js')
const Worker = require('./lib/worker')
const worker = new Worker()

worker.processJobs(
  'housekeeping.createIndex',
  config.redisConnection,
  config.log.level
)

Example minimal local.js

module.exports = {
  redisConnection: {
    port: 6379,
    host: 'localhost'
  },
  log: {
    level: 'debug'
  }
}

License:

The MIT License (MIT)
Copyright © 2022 Press Computer Systems Ltd.

Permission is hereby granted, free of charge, to any person obtaining a
copy of this software and associated documentation files (the “Software”),
to deal in the Software without restriction, including without limitation
the rights to use, copy, modify, merge, publish, distribute, sublicense,
and/or sell copies of the Software, and to permit persons to whom the Software
is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included
in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL
THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.