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
contains, for the "GL" country, the America/Godthab timezone, which has been deprecated, in fact all data files (metadata, unpacked and package latest) contain America/Nuuk instead (which has replaced Godthab).
I have seen that the entry point (index.js) loads the metadata files, but since the package.json tells bundlers to use builds/moment-timezone-with-data.js as the package's entry point, my Angular app contains the deprecated timezone hardcoded in the .js bundle.
Seems like a new version is needed with rebuilt bundles to fix the issue.
The text was updated successfully, but these errors were encountered:
@Etchelon if you really want a slick data package without extra baggage package one yourself. The source data is pretty well documented, and the moment-timezone pipeline is not terrible either.
One thing to note is that we could actually link zones that are the same, instead of copy-pasting their DST points, but nobody has proposed that so far. If somebody implemented it and made a PR it could get merged.
Moment-timezone version which you use:
Version: 0.5.32 (latest right now)
Note: many issues are resolved if you just upgrade to the latest version
Issue description:
node_modules/moment-timezone/builds/moment-timezone-with-data.js
contains, for the "GL" country, the America/Godthab timezone, which has been deprecated, in fact all data files (metadata, unpacked and package latest) contain America/Nuuk instead (which has replaced Godthab).
I have seen that the entry point (index.js) loads the metadata files, but since the package.json tells bundlers to use builds/moment-timezone-with-data.js as the package's entry point, my Angular app contains the deprecated timezone hardcoded in the .js bundle.
Seems like a new version is needed with rebuilt bundles to fix the issue.
The text was updated successfully, but these errors were encountered: