0

Currently, I have a been trying to install a plugin, but the 2 plugins have similar commands and I would like to keep the base command of the plugin I've installed. Adding an extra command to the plugin is hacky and is not a good dev experience. (Ex. devphase devphase init if standalone multi-command CLI and if installed as plugin would look like swanky devphase init).

I don't want to maintain a separate plugin repo or use aliases bc this runs into the same problem of not being a great experience.

Is there a better solution to be able to install a plugin and preserve the base command, such that, the standalone command multi-command CLI can still be devphase init and then if I decide to install it as a plugin in another multi-command CLI called swanky then it will create a sub-command like the following swanky devphase?

I've tried all options in docs including the running commands programmatically, but this involves maintaining 2 separate repos and is not a great solution.

0 Answers0