> Any package that includes a CLI version in the library should have it's dev shamed. Usually that adds 10-20 packages. After your little rant you point out Co

> Any package that includes a CLI version in the library should have it's dev shamed. Usually that adds 10-20 packages. After your little rant you point out Commander has zero dependencies. So I don’t know what’s up with you. If the library you’re building has anything with application lifecycle, particularly bootstrapping, then having a CLI with one dependency is quite handy for triage. Most especially for talking someone else through triage when for instance I was out and there was a production issue. Which is why half the modules I worked on at my last place ended up with a CLI. They are, as a rule, read mostly. Which generally doesn’t require an all caps warning. Does every module need one of those? No. But if your module is meant as a devDependency, odds are good it might. And if it’s bootstrapping code, then it might as well. > should have it's dev shamed Oh I feel embarrassed right now. But not for me.