Include execution `env` option?

Open
#32 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
38/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
javascript
Domain
cli

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.

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?

Dominant language
JavaScript
Stars
147
Forks
22
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from mathisonian/command-exists

All issues in mathisonian/command-exists

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.