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
2.19.1: can no longer combine moment, moment-timezone and moment-business-days #4236
Comments
I believe I am getting something similar. Using
Throws this error:
Rolling back to 2.18.1 it works fine. |
I'm seeing a similar error. require('moment').version // 2.18.1
require('moment') === require('moment-timezone') // true require('moment').version // 2.19.1
require('moment') === require('moment-timezone') //false |
Same for both 2.19.0 and 2.19.1 |
is it going to be fixed any time soon? or is there a known work around for this? staying on 2.18.1 might not be an option much longer... |
Are you sure this issue still exists with Moment 2.24.0 & moment-timezone 0.5.26? If I do:
I don't seem to have a problem using moment.tz |
Please re-open if you still have issues. |
This is still an issue, tho. require('moment').version // 2.24.0 require('moment').version // 2.25.3 require('moment').version // 2.26.0 require('moment').version // 2.27.0 So since version 2.24.0 I cannot set timezones. This is a real bummer. |
I used to be able to combine
moment
,moment-timezone
,moment-business-days
(andmoment-range
but that one isn't a problem in this situation), like so:This worked in all versions before upgrading to 2.19.1. Now I get the following error:
Uncaught TypeError: Cannot read property 'setDefault' of undefined
And i traced it down to
moment.tz
no longer getting defined.The problem is if I
import moment from moment-timezone
thenmoment-business-days
will no longer work.Environment:
Chrome 61 on MacOS 10.12.6
Compiled with webpack
debug output:
Any ideas?
The text was updated successfully, but these errors were encountered: