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

@jorsek/nodejs-worker-library

v1.0.8

Published

Basic node worker library

Downloads

5

Readme

Basic node.js worker

A library for creating node.js workers for Jorsek's publishing system.

Setup - running locally

Make sure you have Node.js installed locally.

This system requires environmental variables to run, the following variables should be defined:

GATEWAY_URL=
GCLOUD_PUBSUB_KEY_FILE=

GATEWAY_URL is the URL to the Internal API Gateway. For local development, it's usually http://localhost:9235/. Please remember about the / at the end.

GCLOUD_PUBSUB_KEY_FILE is the path to the .json file obtained from GCP. This file should be a key to a service account with Pub/Sub read and write access.

If you are using PUBSUB_PREFIX, set this environment variable here as well. Make sure it's the same in easyDITA, Publishing Job Manager and here.