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.

Follow

Last, but not least, implement stuff by yourself. This is basically like bundling, except you're responsible for the code that gets shipped. This adds lots of headache since one now needs to manage a way bigger codebase, but one also gets more control.

Sign in to participate in the conversation
Fosstodon

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