Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Modifying (`.add()`, `.subtract()`, etc.) a dayjs instance created in UTC corrupts it
See original GitHub issueSetting timezone explicitly
dayjs.tz(0, 'UTC').format()
'1970-01-01T00:00:00Z' - Result
'1970-01-01T00:00:00Z' - Expected
dayjs.tz(0, 'UTC').add(0,'minutes').format()
'1969-12-31T23:00:00Z' - Result
'1970-01-01T00:00:00Z' - Expected
dayjs.tz(0, 'UTC').add(1,'minutes').format()
'1969-12-31T23:01:00Z' - Result
'1970-01-01T00:01:00Z' - Expected
Setting default timezone
The above results are identical, when omitting 'UTC' and setting UTC as default:
dayjs.tz.setDefault('UTC')
dayjs.tz(0).format()
'1970-01-01T00:00:00Z' - Result
'1970-01-01T00:00:00Z' - Expected
dayjs.tz(0).add(0,'minutes').format()
'1969-12-31T23:00:00Z' - Result
'1970-01-01T00:00:00Z' - Expected
dayjs.tz(0).add(1,'minutes').format()
'1969-12-31T23:01:00Z' - Result
'1970-01-01T00:01:00Z' - Expected
Information
- Day.js Version 1.11.5
- OS: Mac
- Browser: Chrome
Issue Analytics
- State:
- Created a year ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Yes I tried every combination and found that the problem is the utc time zone (even as gmt e.a.) I am working on it for the last 2 weeks, but i could not yet solve all combinations. At the moment I just have to fix the .tz(‘UTC’) variant.
Please be patient as it will take me for sure a few more days; but I won’t surrender 😃
I could reproduce the issue; working on a solution / pr.