command-exists
npmv1.2.9check whether a command line command exists in the current environment
Not recommended for new projects
No — command-exists should not be adopted for new projects. Last published 2338 days ago.
- ?Adoption: grade ?, Not reported by this registry.
No download data reported for this package yet.
- FMaintenance: grade F, Failing.
Last published 2338 days ago.
- AWeight: grade A, Excellent.
Zero runtime dependencies, about 13 KB installed.
- BSupply chain: grade B, Good.
This package has a single maintainer (bus factor of 1).
- ALicense: grade A, Excellent.
MIT — permissive, with no copyleft found in the dependency tree.
Grades are computed deterministically from registry metadata collected by PackageGraph — downloads, dependents, publish dates, the resolved dependency tree, maintainer count, and declared licenses. No third-party scores are used.
Install cost
What you actually take on by adding command-exists to a project.
Runtime packages this one declares itself.
Distinct packages in the full runtime tree, deduplicated the way a package manager would.
Unpacked size of this package plus its entire runtime tree.
Longest resolved dependency chain below this package.
Compatibility
- Node.js
- No constraint declared
- Module format
- CommonJS only
- TypeScript
- No bundled types
- Install scripts
- None
Quick start
A usage example from the command-exists README.
var commandExists = require('command-exists');
commandExists('ls', function(err, commandExists) {
if(commandExists) {
// proceed confidently knowing this command is available
}
});command-exists vs the alternatives
Packages solving a similar problem in the npm ecosystem, compared on the signals that drive an adoption decision.
| Package | Weekly downloads | Dependents | License | Last release |
|---|---|---|---|---|
| command-existsthis page | 0 | 1 | MIT | 6 years ago |
| commander | 451.1M | 11 | MIT | 1 day ago |
| yargs-parser | 178.8M | 2 | ISC | 1 day ago |
| meow | 36.7M | 1 | MIT | 1 day ago |
| yargs | 0 | 12 | MIT | 1 day ago |
| dashdash | 0 | 1 | MIT | 1 day ago |
Dependencies
Declared by command-exists v1.2.9. Runtime dependencies are installed with the package; dev dependencies are not.
Dev (3)
Used by
Popular packages that depend on command-exists.
Relationship graph
Dependencies (left) and dependents (right) of command-exists.
Frequently installed together
JavaScript parser and stringifier for YAML
The tiniest and the fastest library for terminal output formatting with ANSI colors
A library for deep (recursive) merging of Javascript objects
Elegant terminal spinner
This package is part of the [React Native CLI](../../README.md). It contains commands for managing the configuration of React Native app.
No description provided.
No description provided.
This package is part of the [React Native CLI](../../README.md). It contains utilities for building reusable commands targeting Apple platforms.
This package is part of the [React Native CLI](../../README.md). It contains commands for managing iOS part of React Native app.
Info about your dev environment for debugging purposes
This package is part of the [React Native CLI](../../README.md). It contains commands for managing the Android part of React Native app.
The semantic version parser used by npm.
Release history
No releases in the last two years, typically about 24 days apart.
| Version | Published | Size | License |
|---|---|---|---|
| 1.2.9latest | 6 years ago | 13 KB | MIT |
| 1.2.8 | 8 years ago | 12 KB | MIT |
| 1.2.7 | 8 years ago | 12 KB | MIT |
| 1.2.6 | 8 years ago | 12 KB | MIT |
| 1.2.5 | 8 years ago | 11 KB | MIT |
| 1.2.4 | 8 years ago | 10 KB | MIT |
| 1.2.3 | 8 years ago | 10 KB | MIT |
| 1.2.2 | 9 years ago | — | MIT |
| 1.2.1 | 9 years ago | — | MIT |
| 1.2.0 | 9 years ago | — | MIT |
| 1.1.0 | 9 years ago | — | MIT |
| 1.0.2 | 10 years ago | — | MIT |
| 1.0.1 | 10 years ago | — | MIT |
| 1.0.0 | 10 years ago | — | MIT |
| 0.1.1 | 10 years ago | — | MIT |
Overview
command-exists is an npm package that check whether a command line command exists in the current environment. It has 1 known dependents in the graph. The latest version is 1.2.9, released under the MIT license.
Who should use it
Teams working in the npm ecosystem who need check whether a command line command exists in the current environment and value a focused solution.
When not to use it
Consider an alternative if you need to have first-class TypeScript types out of the box, or if a more actively-maintained option better fits your npm stack.
Pros
- Clear open-source license (MIT).
- Lean dependency tree (3 direct dependencies).
Cons
- No bundled TypeScript types (may require a separate @types package).
Auto-generated from collected registry metadata. No external claims are inferred.
Maintainers
Frequently asked questions
Should I use command-exists?
No — command-exists should not be adopted for new projects. Last published 2338 days ago.
How do I install command-exists?
Run `npm install command-exists` to add command-exists to your npm project.
What license is command-exists released under?
command-exists is distributed under the MIT license.
How popular is command-exists?
npm does not publish download counts. Within PackageGraph's crawl, 1 known packages depend on command-exists.
Is command-exists still maintained?
The most recent release of command-exists (v1.2.9) was published 6 years ago.
Does command-exists run install scripts?
No. command-exists does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.