-
-
Notifications
You must be signed in to change notification settings - Fork 363
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. Weβll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unrecognized time zone identifier: "Europe/Kyiv" #343
Comments
Thanks for letting me know!
I think that's the problem. I'm using |
Regarding to marnusw/date-fns-tz#120 (comment) it may be caused by mismatched nodejs timezones and browser timezones. In firefox v105.0b9: > Intl.DateTimeFormat().resolvedOptions().timeZone
< 'Europe/Kyiv' In edge v105.0.1343.42: > Intl.DateTimeFormat().resolvedOptions().timeZone
< 'Europe/Kiev' But in node v18.8.0 > new Intl.DateTimeFormat('en-US', {timeZone: 'Europe/Kyiv'}).format(Date.now())
Uncaught RangeError: Invalid time zone specified: Europe/Kyiv
at new DateTimeFormat (<anonymous>) > new Intl.DateTimeFormat('en-US', {timeZone: 'Europe/Kiev'}).format(Date.now())
'9/20/2022' Node already updated |
Confirm. In node 18.9.0 both timezone works. > new Intl.DateTimeFormat('en-US', {timeZone: 'Europe/Kyiv'}).format(Date.now())
'9/20/2022'
> new Intl.DateTimeFormat('en-US', {timeZone: 'Europe/Kiev'}).format(Date.now())
'9/20/2022' Therefore, I assume that updating the node on the demo server should solve this problem |
I've updated |
Yeap. Still not working in firefox 109.0b3 on windows 10 |
This is still an issue |
π Describe the bug
On live demo I got this error:
π To Reproduce
π‘ Expected behavior
Just normaly work
πΌοΈ Screenshots
βοΈ Environment
Live demo from README π€·ββοΈ
Browser: Firefox Developer edition v105.0b9
π Additional context
In my opinion it may be related to recently renaming timezone Europe/Kiev to Europe/Kyiv
https://mm.icann.org/pipermail/tz-announce/2022-August/000071.html
The text was updated successfully, but these errors were encountered: