is-interactive
Advanced tools
Weekly downloads
Readme
Check if stdout or stderr is interactive
It checks that the stream is TTY, not a dumb terminal, and not running in a CI.
This can be useful to decide whether to present interactive UI or animations in the terminal.
$ npm install is-interactive
import isInteractive from 'is-interactive';
isInteractive();
//=> true
Type: object
Type: stream.Writable
Default: process.stdout
The stream to check.
ci-info
for the CI check?It's silly to have to detect individual CIs. They should identify themselves with the CI
environment variable, and most do just that. A manually maintained list of detections will easily get out of date. And if a package using ci-info
doesn't update to the latest version all the time, they will not support certain CIs. It also creates unpredictability as you might assume a CI is not supported and then suddenly it gets supported and you didn't account for that. In addition, some of the manual detections are loose and might cause false-positives which could create hard-to-debug bugs.
It's not about the number of lines, but rather discoverability and documentation. A lot of people wouldn't even know they need this. Feel free to copy-paste the code if you don't want the dependency. You might also want to read this blog post.
FAQs
Check if stdout or stderr is interactive
The npm package is-interactive receives a total of 16,309,612 weekly downloads. As such, is-interactive popularity was classified as popular.
We found that is-interactive demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket installs a GitHub app to automatically flag issues on every pull request and report the health of your dependencies. Find out what is inside your node modules and prevent malicious activity before you update the dependencies.