Repository navigation
node -p "Intl.DateTimeFormat().resolvedOptions().timeZone" return undefined for Windows Mountain Time (Alberta) #67262
Description
Version
v24.22.2
Platform
Windows
Subsystem
No response
What steps will reproduce the bug?
- Pick the new Mountain TIme (Alberta) as windows timezone setting
- run node -p "Intl.DateTimeFormat().resolvedOptions().timeZone"
How often does it reproduce? Is there a required condition?
always
What is the expected behavior? Why is that the expected behavior?
should return valid timezone instead of undefined
What do you see instead?
undefined
Additional information
No response
Activity
iqoOopi commentedon Nov 4, 2026
Node might need to use CLDR v49 isntead v48, v49 has the missing zone mapping:
https://github.com/unicode-org/cldr/blob/main/common/supplemental/windowsZones.xml#L87
Renegade334 commentedon Nov 5, 2026
I imagine this will be picked up with the ICU 79 update.
jismonthomas commentedon Nov 5, 2026
same issue here in B.C, timezone is undefined since Nov 1