Command seems to implicitly include the help plugin

[robcresswell]

This seems to rely on the help plugin, which rather defeats the object of a plugin; it also makes it non-trivial to write your own help command.

[G-Rath]

It seems this was done by request as part of #66

[jasonk]

You don't mention what kind of problems you are running into, but even though it's a dependency, the thing that adds it to your CLI is that the plugin is listed by default in oclif.plugins in package.json. If you remove it from there then help doesn't get listed in the default output any more.

[robcresswell]

You don't mention what kind of problems you are running into

Sorry for not being clear on this, but this is what I meant by "it also makes it non-trivial to write your own help command.". Its hard to recall exactly what my problem was; this was nearly 3 months ago. I believe the inclusion of this meant I couldn't write my own help plugin, as the default one got called because of it being a dep.

If you remove it from there then help doesn't get listed in the default output any more.

While it removes it from the list, running help still seems to show the help text in the OCLIF format. So I'm guessing the plugin mechanism picks it up somehow?