Bower Support

[jkillian]

Although not ideal, I'm in a situation where installing the package via NPM doesn't meet my use case as we're not using browserify, webpack or anything like that. Is there a current usage story for using this via bower? If not, would you be interested in a contribution to make it more bower friendly?

[gpbl]

Yes thanks! I have no idea how does bower work, but sure it would be nice to support it.

[gpbl]

Woah I've made some crazy things with bower register, npm publish etc... 👯 now it should work everything as version 1.1.3.

@jkillian Could you please test if it actually works with bower and eventually close the issue? I don't get why it doesn't appear in their search...

[jkillian]

@gpbl I see it in the search now - probably just a caching issue! I'll try it out now

[jkillian]

Working like a charm in my project 👍

[jkillian]

Right now we're only exposing the DayPicker React class as a global variable named DayPicker. Do you think instead we should export an object called DayPicker and then it could have the following fields:

• DayPicker
• LocalUtils
• MomentLocaleUtils
• Helpers
• DateUtils

or something similar to that?

[gpbl]

I was wondering as well... we should however export only the "official" API.

I don't know what are the common practices for a bower component, but I imagine:

DayPicker
DayPicker.localeUtils
DayPicker.dateUtils
DayPicker.momentLocaleUtils

I think we can add some static properties to DayPicker when exporting it, so that the component is actually <DayPicker /> and not <DayPicker.DayPicker> or, as I thought at first, <DayPicker.Component />.

(I'm not so happy for this *Utils convention , how would you call them?)

[jkillian]

Actually, I think the *Utils names are pretty clear, they make sense to me. Do you want to go ahead and do this or want me to take a shot at it?

[gpbl]

I have no interest in bower so I'd really appreciate a PR 🖖. (pay attention to that momentLocaleUtils, because it requires moment but I won't put moment as dependency. Maybe you need some "ignore" setting in the webpack config).

Deep thanks for your support, JKillian!

[jkillian]

I think PR #93 should take care of things here. Let me know once you release and I'll test it out!