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

@qawolf/ci-info

v2.1.0

Published

Get details about the current Continuous Integration environment

Downloads

4,895

Readme

ci-info

Get details about the current Continuous Integration environment.

Please open an issue if your CI server isn't properly detected :)

npm Build status js-standard-style

Installation

npm install ci-info --save

Usage

var ci = require('ci-info')

if (ci.isCI) {
  console.log('The name of the CI server is:', ci.name)
} else {
  console.log('This program is not running on a CI server')
}

Supported CI tools

Officially supported CI servers:

| Name | Constant | isPR | |------|----------|------| | AWS CodeBuild | ci.CODEBUILD | 🚫 | | AppVeyor | ci.APPVEYOR | ✅ | | Azure Pipelines | ci.AZURE_PIPELINES | ✅ | | Bamboo by Atlassian | ci.BAMBOO | 🚫 | | Bitbucket Pipelines | ci.BITBUCKET | ✅ | | Bitrise | ci.BITRISE | ✅ | | Buddy | ci.BUDDY | ✅ | | Buildkite | ci.BUILDKITE | ✅ | | CircleCI | ci.CIRCLE | ✅ | | Cirrus CI | ci.CIRRUS | ✅ | | Codeship | ci.CODESHIP | 🚫 | | Drone | ci.DRONE | ✅ | | dsari | ci.DSARI | 🚫 | | GitHub Actions | ci.GITHUB_ACTIONS | ✅ | | GitLab CI | ci.GITLAB | 🚫 | | GoCD | ci.GOCD | 🚫 | | Hudson | ci.HUDSON | 🚫 | | Jenkins CI | ci.JENKINS | ✅ | | Magnum CI | ci.MAGNUM | 🚫 | | Netlify CI | ci.NETLIFY | ✅ | | Nevercode | ci.NEVERCODE | ✅ | | Sail CI | ci.SAIL | ✅ | | Semaphore | ci.SEMAPHORE | ✅ | | Shippable | ci.SHIPPABLE | ✅ | | Solano CI | ci.SOLANO | ✅ | | Strider CD | ci.STRIDER | 🚫 | | TaskCluster | ci.TASKCLUSTER | 🚫 | | TeamCity by JetBrains | ci.TEAMCITY | 🚫 | | Travis CI | ci.TRAVIS | ✅ |

API

ci.name

Returns a string containing name of the CI server the code is running on. If CI server is not detected, it returns null.

Don't depend on the value of this string not to change for a specific vendor. If you find your self writing ci.name === 'Travis CI', you most likely want to use ci.TRAVIS instead.

ci.isCI

Returns a boolean. Will be true if the code is running on a CI server, otherwise false.

Some CI servers not listed here might still trigger the ci.isCI boolean to be set to true if they use certain vendor neutral environment variables. In those cases ci.name will be null and no vendor specific boolean will be set to true.

ci.isPR

Returns a boolean if PR detection is supported for the current CI server. Will be true if a PR is being tested, otherwise false. If PR detection is not supported for the current CI server, the value will be null.

ci.<VENDOR-CONSTANT>

A vendor specific boolean constant is exposed for each support CI vendor. A constant will be true if the code is determined to run on the given CI server, otherwise false.

Examples of vendor constants are ci.TRAVIS or ci.APPVEYOR. For a complete list, see the support table above.

Deprecated vendor constants that will be removed in the next major release:

  • ci.TDDIUM (Solano CI) This have been renamed ci.SOLANO

License

MIT