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 🙏

© 2026 – Pkg Stats / Ryan Hefner

rit-devops

v1.3.1

Published

Quick-reference CLI for common Dockerfile and Jenkinsfile templates (Java, Maven, Python, Flask, React) with Docker Swarm / Kubernetes deploy stages.

Readme

rit-devops

A quick-reference CLI for common Dockerfile and Jenkinsfile templates (Java, Maven, Python, Flask, React) with Docker Swarm / Kubernetes deploy stages.

Usage

npx rit-devops                 # show everything (dockerfiles + jenkinsfiles + swarm-config + minikube + your config notes)
npx rit-devops dockerfile       # show only the Dockerfile templates
npx rit-devops jenkins          # show only the Jenkinsfile templates
npx rit-devops swarm-config     # show the Docker Swarm cluster setup guide (VirtualBox + Vagrant)
npx rit-devops minikube         # show the Minikube + kubectl local Kubernetes setup guide
npx rit-devops config           # view saved config notes
npx rit-devops config "text"    # save a new config note
npx rit-devops config --clear   # clear all saved config notes
npx rit-devops --help           # show all commands
npx rit-devops -v               # show version

Config notes are stored locally per-user at ~/.rit-devops/config.json, so they persist across runs on the same machine.

Publishing this package to npm

You said you already have an npm account, so here's exactly what to do:

  1. Install Node.js if you don't already have it (v14+): https://nodejs.org

  2. Log in to npm from your terminal:

    npm login

    This will ask for your username, password, and email (and possibly a one-time 2FA code).

  3. Move into the project folder (unzip the file I gave you first):

    cd rit-devops
    npm install
  4. Test it locally before publishing (optional but recommended):

    node bin/cli.js --help
    node bin/cli.js dockerfile

    Or link it globally to test the real rit-devops command:

    npm link
    rit-devops --help
  5. Publish:

    npm publish

    That's it — rit-devops was free on the registry when I checked, so this should succeed on the first try. If you get a 403/name-taken error, someone grabbed it in the meantime; just rename it in package.json (name field) and in the bin field, then publish again.

  6. From then on, anyone (including you) can run it with:

    npx rit-devops

    npx automatically downloads and runs the latest published version — no separate install step needed.

Publishing updates later

Whenever you edit the templates or add features:

npm version patch   # bumps 1.0.0 -> 1.0.1 (use "minor" or "major" for bigger changes)
npm publish

Project structure

rit-devops/
├── bin/
│   └── cli.js          # CLI entry point (uses Commander.js)
├── lib/
│   ├── dockerfiles.js  # Dockerfile template data
│   ├── jenkinsfiles.js # Jenkinsfile template data
│   ├── swarmConfig.js  # Docker Swarm (VirtualBox + Vagrant) setup guide
│   ├── minikube.js     # Minikube + kubectl setup guide
│   └── config.js       # reads/writes ~/.rit-devops/config.json
├── package.json
└── README.md

To add more templates, just add new { title, content } entries to the arrays in lib/dockerfiles.js or lib/jenkinsfiles.js.