Current Path: > > usr > lib > node_modules > npm > > node_modules > is-ci
Operation : Linux host59.registrar-servers.com 4.18.0-513.18.1.lve.2.el8.x86_64 #1 SMP Sat Mar 30 15:36:11 UTC 2024 x86_64 Software : Apache Server IP : 198.54.126.42 | Your IP: 216.73.216.9 Domains : 1034 Domain(s) Permission : [ 0755 ]
Name | Type | Size | Last Modified | Actions |
---|---|---|---|---|
node_modules | Directory | - | - | |
LICENSE | File | 1091 bytes | March 10 2021 14:36:39. | |
README.md | File | 1299 bytes | March 10 2021 14:36:39. | |
bin.js | File | 70 bytes | March 10 2021 14:36:39. | |
index.js | File | 55 bytes | March 10 2021 14:36:39. | |
package.json | File | 1663 bytes | March 10 2021 14:36:39. |
# is-ci Returns `true` if the current environment is a Continuous Integration server. Please [open an issue](https://github.com/watson/is-ci/issues) if your CI server isn't properly detected :) [](https://www.npmjs.com/package/is-ci) [](https://travis-ci.org/watson/is-ci) [](https://github.com/feross/standard) ## Installation ```bash npm install is-ci --save ``` ## Programmatic Usage ```js const isCI = require('is-ci') if (isCI) { console.log('The code is running on a CI server') } ``` ## CLI Usage For CLI usage you need to have the `is-ci` executable in your `PATH`. There's a few ways to do that: - Either install the module globally using `npm install is-ci -g` - Or add the module as a dependency to your app in which case it can be used inside your package.json scripts as is - Or provide the full path to the executable, e.g. `./node_modules/.bin/is-ci` ```bash is-ci && echo "This is a CI server" ``` ## Supported CI tools Refer to [ci-info](https://github.com/watson/ci-info#supported-ci-tools) docs for all supported CI's ## License [MIT](LICENSE)
SILENT KILLER Tool