moment-timezone > 0.5.28 breaks Angular build
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Fix Released
|
High
|
Unassigned | ||
3.4 |
Fix Released
|
High
|
Unassigned |
Bug Description
Starting with 0.5.29, moment-timezone now includes [0] an index.d.ts that adds Typescript type definitions. Unfortunately, this breaks how moment-timezone has been used to date. Here's an example of the ng build errors:
ERROR in app/core/
164 momentizeIsoStr
app/core/
171 momentizeDateSt
app/core/
178 momentizeDateTi
app/core/
Pinning moment-timezone to its current value of 0.5.27 rather than ^0.5.27 avoids the error, although we should figure out how to properly import and use a Typescript-
[0] https:/
Evergreen master
Changed in evergreen: | |
assignee: | nobody → Jane Sandberg (sandbej) |
Changed in evergreen: | |
assignee: | Jane Sandberg (sandbej) → nobody |
status: | New → Confirmed |
Changed in evergreen: | |
assignee: | nobody → Bill Erickson (berick) |
Changed in evergreen: | |
assignee: | nobody → Galen Charlton (gmc) |
Changed in evergreen: | |
status: | Fix Committed → Fix Released |
Setting importance to "high" because this is just an npm update away from being a constant build problem.