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.


Bundling dependencies + tree shaking can allow you to ship smaller bundles, but the dependencies will get outdated pretty quickly, unless you use dependabot or something to automatically push updates. Smaller size, yet less practical. And if one of your dependencies will have a vulnerability in it, your users won't find out

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.