Poll for the JS folk!

Suppose there is a JS-based CLI application. It's not that standalone, but rather used in other projects. Like a build system or a linter.

The CLI has some dependencies. Not a lot and not critical, but still. Stuff like colour and CLI manager, perhaps some concurrency library and other utility stuff

What would be your way of delivering it to the end user? I'll go over my personal pros and cons in the replies.


Defining dependencies as dependencies has a benefit of not having to release a new version every time the dependency gets an update. The end user can run `npm up` and the newer versions will be downloaded automatically.

The con of this is the fact that everything gets downloaded. ReadMe, licence headers, in some cases even source code. And, of course, code that never gets executed in your CLI app. Kinda too much download size.

Sign in to participate in the conversation

Fosstodon is an English speaking Mastodon instance that is open to anyone who is interested in technology; particularly free & open source software.