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

@allanoricil/node-red-private-catalogue-builder

v0.1.4

Published

A minimal web app to host a `catalogue.json` file for a private repository of Node-RED nodes.

Downloads

27

Readme

node-red-private-catalogue-builder

A minimal web app to host a catalogue.json file for a private repository of Node-RED nodes.

Configure

Environment variables:

  • NAME - catalogue name (defaults to verdaccio)
  • PORT - which port to listen on (defaults to 8080)
  • HOST - which local IP Address to bind to (defaults to 0.0.0.0)
  • REGISTRY - a host and optional port number to connect to the NPM registry (defaults to http://localhost:4873)
  • KEYWORD - the npm keyword to filter on (defaults to node-red)

It exposes 3 endpoints:

GET   /health         used to check the status of the service
POST  /update         rebuilds the catalogue
GET   /catalogue.json returns the current catalogue

The GET /update route is called by Verdaccio every time it changes something:

notify:
  method: POST
  headers: [{'Content-Type': 'application/json'}]
  endpoint: http://catalogue/update
  content: '{"name": "{{name}}", "versions": "{{versions}}", "dist-tags": "{{dist-tags}}"}'

Build

docker build . -t catalogue --no-cache

Run

docker run -dit --network=host -e NAME="MY CATALOG" -e REGISTRY="http://localhost:4873" catalogue