felipernb/algorithms.js

Add to Bower

HiroAgustin opened this issue · 3 comments

Adding the library to Bower would make it easier to use on front end projects than npm.

Bower is a package manager for the web. It offers a generic, unopinionated solution to the problem of front-end package management, while exposing the package dependency model via an API that can be consumed by a more opinionated build stack.

http://bower.io/#defining-a-package

Adding the library to Bower would make it easier to use on front end projects than npm.

Opinions may vary regarding that statement.

Do keep in mind that by supporting Bower you'll add _Yet Another Thing_™ to your deploy step. Also, by no means is Bower the defined standard for package management. If you're adding Bower, please also consider deploying to Normalize.io and Component(1) for the sake of completion.

@yoshuawuyts you are right. My intention was to create a "take under consideration" kind of issue.

We can revisit that in the future, but for the sake of simplicity I think I'm gonna stick to just npm for now (https://www.npmjs.org/package/algorithms).

With packages like browserify or quickstart it should be easy to use node modules in the front-end as well.