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

ci-relay

v0.1.4

Published

Tiny CI status aggregation service built on top of ci-adapter and ci-router

Downloads

11

Readme

ci-relay

Tiny CI status aggregation service built on top of ci-adapter and ci-router

Install

To install the required dependencies, you need npm:

$ npm install

Setup

Have a look at the config-example.json file. Copy it to config.json and replace the defaults with something meaningful.

If left blank, the port and host configuration options will use the $PORT and $HOST environment variables, defaulting to localhost:3100 if unspecified.

The example configuration serves the CI status of:

For detailed information on available adapter options refer to ci-adapter.

Start

Once the configuration and dependencies are in place, just type:

$ npm start

That's it! Your CI API should now be running on http://localhost:3100 (or the port you specified in your configuration).