Detect whether a terminal supports color.
Used in the terminal color module chalk.
$ npm install --save has-color
var hasColor = require('has-color');
if (hasColor) {
console.log('Terminal supports color.');
}
It obeys the --color and --no-color CLI flags.
MIT © Sindre Sorhus
The supports-color package is similar to has-color but provides more detailed information about the terminal's color capabilities. It can detect the level of color support (basic, 256, or truecolor) and is more feature-rich compared to has-color.
Chalk is a popular package for styling terminal strings. While its primary purpose is to add color and style to terminal output, it also includes functionality to detect if the terminal supports color, making it a more comprehensive solution compared to has-color.
Ansi-colors is another package for styling terminal output with ANSI colors. It includes utilities to check for color support and provides a wide range of styling options, making it a more versatile option compared to has-color.
FAQs
Detect whether a terminal supports color
The npm package has-color receives a total of 563,656 weekly downloads. As such, has-color popularity was classified as popular.
We found that has-color 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 for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Research
Five malicious NuGet packages impersonate Chinese .NET libraries to deploy a stealer targeting browser credentials, crypto wallets, SSH keys, and local files.
Security News
pnpm 11 turns on a 1-day Minimum Release Age and blocks exotic subdeps by default, adding safeguards against fast-moving supply chain attacks.
Security News
The remediated findings include organization permission bugs, stale project access after transfers, OIDC replay edge cases, audit logging gaps, and an IDOR in API token deletion.