Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Why did you start splitting out the CLIs from your modules? #17

Closed
matiassingers opened this issue Jul 1, 2015 · 1 comment
Closed

Comments

@matiassingers
Copy link

matiassingers commented Jul 1, 2015

Just wondering what your thought process was behind the sudden change in style. For example, opn and opn-cli.

@sindresorhus
Copy link
Owner

sindresorhus commented Jul 2, 2015

I've mostly been doing all-in-one modules for convenience, but one day I realized they're actually different concepts. Some users found it confusing that a module has different behavior when installed globally than when installed locally. Having CLI and API in one module also adds a lot of extra dependencies which bloats the package. And the readme get's kinda messy with both API and CLI docs. The pageres readme before the CLI+API split was huge. Many users also never realized many packages of mine had a CLI, as it was included in the normal package. Having a package foo and one called foo-cli makes it clear that the latter is a CLI. And I make sure to cross-link them in a Related section in the readme.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants