OK, the offending code on our part basically boils down to this:
moment.utc(timeStamp).tz(settings.timeAxis.timeZone).utcOffset()
The fact that it crashed only on the .utcOffset()
call means that Moment is actually loaded fine. My guess is that it just does not recognize the time zone specified for the time axis.
In retrospect, we should probably handle this case better and emit a pretty error message. I'll fix that later, but it won't help you much. Can you please confirm that the time zone setting for the time axis is one that Moment does not recognize? Perhaps try executing the above calls yourself and see if it works in console.