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

@pch-ng/builder

v0.2.6

Published

Common build scripts

Downloads

1

Readme

PCH builder

Install with

yarn add @pch-ng/builder

It provides three npm commands:

ci-build

Builds the Docker image and pushes it to the propertyconnect Quay.io Docker registry. Also adds a git tag and pushes it, so a SSH key with write access must be supplied.

Required env vars:

  • CIRCLE_PROJECT_REPONAME (provided by Circle CI)
  • CIRCLE_BUILD_NUM (provided by Circle CI)
  • CIRCLE_BRANCH (provided by Circle CI)
  • QUAYIO_USER
  • QUAYIO_PASSWORD

ci-trigger-deploy

Triggers the deploy task on Circle CI. The deployment will be done with the tag created by ci-build.

Required env vars:

  • CIRCLE_PROJECT_USERNAME (provided by Circle CI)
  • CIRCLE_PROJECT_REPONAME (provided by Circle CI)
  • CIRCLE_BUILD_NUM (provided by Circle CI)
  • CIRCLE_BRANCH (provided by Circle CI)
  • CIRCLE_SHA1 (provided by Circle CI)
  • CIRCLE_API_TOKEN — API token which allows the script to trigger a build

ci-deploy

Upgrades a service on Rancher. Is triggered by ci-trigger-deploy with the Docker image tag to deploy.

Required env vars:

  • CIRCLE_PROJECT_REPONAME (provided by Circle CI)
  • RANCHER_API_URL
  • RANCHER_ENV — Rancher environment identifier (e.g. 1a5)
  • RANCHER_SERVICE — Rancher service identifier (e.g. 1s12)
  • TAG_TO_DEPLOY (provided by ci-trigger-deploy, defaults to master if not set)