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

knube-deploy

v0.1.0-rc.16

Published

Easily manage Docker images and Kubernetes manifests for deployment from your machine or CI. Inspired by a custom Ruby tool built by the LiveRamp DevOps team.

Readme

knube_deploy

CLI for templating, deploying and archiving Kubernetes manifests

Installation

$ npm i --save-dev knube-deploy

- OR -

$ yarn add --dev knube-deploy

TODO

Usage

Configuration

deploy.yaml

Most global configuration is defined in a deploy.yaml that should be in the root directory of your project. knube-deploy operates on the concept of "target clusters," and each command described in "Usage" will iterate on each context item defined.

# minimal deploy.yaml
contexts:
- name: production
  context: gke_my-app-project_us-west1_prod-cluster
  image: myapp-prod
  imageRegistry: gcr.io/my-app-project
- name: staging
  context: gke_my-app-project_us-west1_staging-cluster
  image: myapp-staging
  imageRegistry: gcr.io/my-app-project
- name: local 
  context: minikube
  image: myapp
  imageRegistry: local-registry

docker

TODO

kubectl

TODO

Archive Storage

Multiple backends are available for storing the archive tarballs during the kube:publish step. Options include:

  1. devnull: No-op storage-- rendered manifests must be available locally for kube:deploy to succeed
  2. localstorage: Uses a configurable directory on the local filesystem
  3. gcs: Use a Google Cloud Storage bucket (not yet implemented)
  4. s3: Use an AWS S3 bucket (not yet implemented)
  5. azure: Use Azure cloud storage (not yet implemented)
  6. github: Use Github Artifact storage (not yet implemented)
  7. gitlab: Use Gitlab Artifact storage (not yet implemented)
  8. artifactory: Use Artifactory artifact storage (not yet implemented)

Commands

docker:build

Build a docker image with the specified configuration.

args

TODO

kube:generate

Render manifests from the input directory of EJS templates.

args

TODO

kube:publish

Push the built docker image to the configured registry, then create a tarball archive of rendered manifests and push it to the configured archive storage backend.

args

TODO

kube:deploy

Fetch and unzip the manifest tarball for the specified version, then kubectl apply its contents in the configured context(s).

args

TODO

fortytwo

Answer to the Ultimate Question of Life, the Universe and Everything

Runs all of the above in order.

args

Takes all arguments from the above commands.

In CI/CD / Non-Interactive Modes

TODO

Development

TODO