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

get-ci-env

v2.0.0

Published

Get and normalize continuous integration service environment variables.

Downloads

22

Readme

get-ci-env

Travis Build Status LGTM Grade npm

Get and normalize the environment variables from continuous integration services. This package is similar to pvdlg's env-ci but goes for a simpler approach. This results in a more restricted and lightweight (zero dependencies) package:

  • Only CI services that contain all expected values in the environment are supported, taking away the need to manually check the returned data.
  • Return a promise to indicate if a valid CI environment is detected for explicit error handling.
  • Logically nested data for concise naming and easy detection of pull request context: if (ciEnvOutput.pr) { ... }.

Install

npm install get-ci-env

Usage

Example usage when running inside Buildkite:

import getCiEnv from 'get-ci-env';

getCiEnv().then(console.log);

Resulting in the output:

{
  service: 'buildkite',
  branch: 'add-long-eared',
  commit: '1ef3f7c',
  repo: { owner: 'Selwyn', name: 'hedgehogs' },
  pr: { number: '3', branch: 'master' },
}

Supported services

Variables

  • service: Camel-cased CI service name
  • branch: Name of the the branch being built
  • commit: Commit SHA hash that triggered the CI build
  • repo:
    • owner: Name of the repository owner
    • name: Repository name
  • pr: Only set when triggered by a pull request
    • number: Pull request number
    • targetBranch: Name of the base branch that the pull request is targeting

API

getCiEnv(env)

env

Type: object
Default: process.env
The user environment.