@oclif/plugin-which
Advanced tools
find which plugin a command is in
$ npm install -g @oclif/plugin-which
$ oclif-example COMMAND
running command...
$ oclif-example (-v|--version|version)
@oclif/plugin-which/1.0.0 linux-x64 node-v10.1.0
$ oclif-example --help [COMMAND]
USAGE
$ oclif-example COMMAND
...
oclif-example which COMMANDshow which plugin a command is in
USAGE
$ oclif-example which COMMAND
See code: src/commands/which.ts
The 'which' package is a standalone utility for finding the path of an executable in the system's PATH. It is similar to @oclif/plugin-which but is not specific to the Oclif framework. It can be used in any Node.js application to locate executables.
The 'command-exists' package checks if a command-line command exists in the system's PATH. It is similar to @oclif/plugin-which in that it helps locate commands, but it focuses on checking the existence of commands rather than providing their paths.
FAQs
find which plugin a command is in
The npm package @oclif/plugin-which receives a total of 285,162 weekly downloads. As such, @oclif/plugin-which popularity was classified as popular.
We found that @oclif/plugin-which demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 2 open source maintainers 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
/Security News
A mini Shai-Hulud campaign compromised Red Hat Cloud Services npm packages to steal developer and CI/CD secrets during installation.
Research
/Security News
The North Korean malware loader hides in a Packagist-listed package and its GitHub branch to fetch and execute remote code in a likely Contagious Interview-style lure.
Security News
The Rust project is moving toward formal rules on LLM use in contributions after months of internal debate over maintainer burden, code quality, and contributor experience.