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

Add to Bower #25

Closed
HiroAgustin opened this issue May 30, 2014 · 3 comments
Closed

Add to Bower #25

HiroAgustin opened this issue May 30, 2014 · 3 comments

Comments

@HiroAgustin
Copy link

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

@yoshuawuyts
Copy link

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.

@HiroAgustin
Copy link
Author

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

@felipernb
Copy link
Owner

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.

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

3 participants