-
Notifications
You must be signed in to change notification settings - Fork 743
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 missing bower.json #42
Comments
I am reluctant to include more than one package metadata file. I don't want to have to add and maintain a package.json, bower.json and component.json etc. for my repos. It is a shame that bower does not fall back to the package.json 'main' property, but I don't want to get into all that... |
Shame. We could have done with one as well. Obviously we could fork and add it but keeping the fork in sync is not ideal for us. |
The library is registered with bower and if a user just wants to install the main file (should that be bignumber.js or bignumber.min.js?) they can just do e.g.
|
Thanks for the reply Mike! Unfortunately the issue is that we have custom dependency/build scripts that reply on our third party libraries having bower.json files :( Should I get time (?) I would like to investigate changing this (i'm fairly new to the project). Personally I don't want a hard dependency on bower (useful that it is). |
Had the same problem with bower.json's "main" property. Our scripts rely on that property to build the project - similar with what @metaman described. |
@nicolaes Okay, I'll add a bower.json tomorrow. |
Thanks @MikeMcl . |
bower.json added in v2.0.6 |
Adding the missing bower.json would be very nice to work with bower. It can download the project but it's not able to know which file to include, which is the exact purpose of the "main" property of the bower.json.
For more infos on how to do it, refer to the following issue: CreateJS/SoundJS#76
The text was updated successfully, but these errors were encountered: