feat: expose getCliCommand
function
#164
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
To enhance the use of
ni
as part of other CLI packages, this extracts part of therun
function into a separategetCliCommand
function and exports it. This enables CLI authors such as myself to get a full CLI command, including the agent, without necessarily having to invoke it withexecaCommand
(whichrun
does`).My use case is that I need to invoke
execaCommand
myself, because I need to provide it with customstdio
config. I would also be happy with aexecaOptions
config option to enable this use case, but I imagine extractinggetCliCommand
enables more use cases / provides more flexibility and is thus more useful. I happen to useexeca
too, but others might not.Additional context
I have not added any tests since I don't see any for the other top-level functions. Please advise on how/where to add any, if necessary.