-
-
Notifications
You must be signed in to change notification settings - Fork 159
Months are computed wrongly when using format-locale in a negative offset timezone #817
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
Comments
Made a PR #818 that I think will fix this problem. I believe it just occurs in negative timezone offsets, because as the ISO 8601 strings used to compute month dates are always something like |
Well, the bug exists in this package for at least 9 months, made the PR above to fix the problem and it was closed because the maintainer has a simpler fix.. As I don't want to wait for this fix, as I dont know if it will be in the next day or the next year, I'm closing the issue. |
WIll keep it open, as it will be fixed in the next release |
Describe the bug
When using the prop
format-locale
with a browser using a timezone different fromUTC
(probably timezones with negative offsets likeAmerica/Sao_Paulo
), the months of a year are computed wrong, from December to November.To Reproduce
Set your browser timezone to a value different from
UTC
or+00:00
, then use adate-fns
locale as a value of the propformat-locale
Codesandbox: https://codesandbox.io/p/devbox/prod-glitter-lm5nsv
Expected behavior
The months should be in the correct order from January to December
Screenshots

Desktop & mobile (please complete the following information):
The text was updated successfully, but these errors were encountered: