mathisonian / mathisonian/command-exists
Include execution `env` option?
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 147
- Forks
- 22
- PR merge metrics
- No merged PRs in 30d
Description
I realise this project is probably not getting much attention at the moment which is totally fine & understandable.
I just wanted to suggest that it might benefit from taking an `env` option like `child_process.exec` does so that someone can say "does this command exist given this environment." I'm in the position of needing that at the moment and will have to look around for other options.
I guess it is both a relatively niche feature and also something that would fit quite naturally into the module?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are named. Start by locating the module's public command-existence entry point and reviewing how it invokes command checks, then compare the requested option with Node.js child_process.exec env behavior. Done means callers can supply an env option and command existence is evaluated under that environment.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100