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

shipherd

v0.1.0

Published

Watches CI for broken/fixed builds, and posts updates to Slack.

Downloads

4

Readme

Intro

Shipherd is a runnable service for reporting CI statuses to Slack. Only supports CircleCI at the moment.

Features:

  • Messages a channel when a build is broken:
  • Messages a channel when a build is fixed:

Setup

  1. Install from npm:
$ npm install -g shipherd
  1. Rename sample.js to production.js, and replace the values with your personal tokens/urls/configs.

Usage

To start the service, run shipherd start. It's highly recommended to do this in a screen or tmux session (optionally with an auto log).

Config

To edit config values, run shipherd config. This will modify config/production.js.

The config file template lives in config/default.js. This is the base template inherited by all other configs. Any values which are undefined that aren't overridden by another config will throw a runtime error on access, so make sure to add values for these!

A sample config lives at config/sample.js.