-
Notifications
You must be signed in to change notification settings - Fork 397
Change from moment dependency to moment-timezone #234
Conversation
… not able to find moment-timezone module
Hi, thanks for the contribution! This going to break a lot of existing code (not everyone uses browserify or webpack). Did you try requiring |
I did. I've spent about two hours or more trying to come up with a workaround before coming to this solution. However, if others aren't webpack or browserify this doesn't affect them at all as it doesn't change the global injection (only amd and commonJS style) The tests still pass that were written for the global style includes since it's injected via a script tag. |
There are also require.js users. I believe this can still be worked around by using angular.js dependency injection and overriding the Can you please have a look at it and see if this does the trick? |
Well don't I feel like an idiot... one... simple... line of code. Thank you! Also, for some weird reason beta 5 doesn't throw the error that I am seeing in beta 4. So I will upgrade to beta 5 and also keep |
Also, I appreciate the help and the fast response. Great library! |
Thanks Kyle! Any chance you can send a PR with an update to |
Is there any way of doing this without require? |
moment-timezone
replacesmoment
when installed via npm (installation instructions here). Due to the require statements asking formoment
instead ofmoment-timezone
, it's impossible to getmoment.tz
to be defined. Changing the package.json dependency from moment to moment-timezone brings back expected functionality when using tools such as browserify and webpack.