Add missing bower.json about bignumber.js

[MikeMcl]

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...

[metaman]

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.

[MikeMcl]

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.

bower install --save https://raw.githubusercontent.com/MikeMcl/bignumber.js/master/bignumber.min.js

[metaman]

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).

[nicolaes]

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.
Unfortunately we had to rely on big.js but the development is hindered due to it's reduced feature set.
Would love to see an update on this.

[MikeMcl]

@nicolaes Okay, I'll add a bower.json tomorrow.
Do you think the "main" file should be bignumber.js or bignumber.min.js?

[nicolaes]

Thanks @MikeMcl .
As bower automatic dependencies are almost always used with build scripts that include minification I suggest going with "main": "bignumber.js" - as you did in the big.js library :)
If there is need I can also lend a hand with the development around, by the way.

[MikeMcl]

bower.json added in v2.0.6