You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The latest release has changed the behavior when UTC is configured on the server. Previously, UTC was reported as Etc/UTC and now it's reported as Etc/Universal. This breaks downstream dependencies that rely on on detecting Etc/UTC (for better or worse), for example https://github.com/gautamsi/ews-javascript-api.
Reproduction script:
guess.js:
const moment = require('moment-timezone');
console.log(moment.tz.guess());
With 0.5.14:
$ TZ=Etc/UTC node guess.js
Etc/UTC
With 0.5.15:
$ TZ=Etc/UTC node guess.js
Etc/Universal
This looks to be due to the change in the data files, the 2017c version contains "Etc/UTC|UTC|0|0|", whereas the 2018d version contains "Etc/Universal|UTC|0|0|",.
The text was updated successfully, but these errors were encountered:
The latest release has changed the behavior when UTC is configured on the server. Previously, UTC was reported as
Etc/UTC
and now it's reported asEtc/Universal
. This breaks downstream dependencies that rely on on detectingEtc/UTC
(for better or worse), for example https://github.com/gautamsi/ews-javascript-api.Reproduction script:
guess.js:
With 0.5.14:
With 0.5.15:
This looks to be due to the change in the data files, the 2017c version contains
"Etc/UTC|UTC|0|0|",
whereas the 2018d version contains"Etc/Universal|UTC|0|0|",
.The text was updated successfully, but these errors were encountered: