GMT offset incorrectly reported by format method
- Dominant language
- JavaScript
- Stars
- 48.7k
- Forks
- 2.5k
- PR merge metrics
- No merged PRs in 30d
Description
**Describe the bug**
GMT offset is incorrectly reported by the format method but appears to be correctly handled by the browser's `Date` object.
**Expected behavior**
See screenshot below. GMT offsets are reported as `-06:00` both before and after DST change on March 14th, 2021. However, the internal `Date` object reports the correct GMT offset.
**Information**
- Day.js Version: Latest from day.js.org today, tested on the browser's Dev Tools
- OS: Arch Linux
- Browser: Google Chrome Version 88.0.4324.150 (Official Build) (64-bit)
- Time zone: GMT-06:00 (Central Standard Time)
Contributor guide
Research direction
No source file or test is named. Start by reproducing the Day.js format output in Chrome for the Central time zone immediately before and after the March 14, 2021 DST change, then compare it with the browser Date object's GMT offset. Done means the format method reports the correct offset across that transition.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100