Node assuming Summer Time that no longer exists (Brasilia)

[igorcferreira]

• Version: v12.13.0
• Platform: Darwin Kernel Version 19.0.0: Thu Oct 17 16:17:15 PDT 2019; root:xnu-6153.41.3~29/RELEASE_X86_64 x86_64

This is the first year since Brazil abolished summer time. But, Node still assumes that the country is on summer time. This affects calls like toTimeString, and others time formatters.

Example:

$ node
Welcome to Node.js v12.13.0.
Type ".help" for more information.
> (new Date).toUTCString()
'Fri, 08 Nov 2019 15:35:53 GMT'
> (new Date).toTimeString()
'13:36:00 GMT-0200 (Brasilia Summer Time)'
> .exit
$ date
Fri Nov  8 12:36:19 -03 2019

The $ date shows what the system (macOS 10.15.1 [19B88]) shows. The correct timezone for Brazil (at the moment of this report) is GMT-03:00, not GMT-02:00 as Node.js tries to use.

[richardlau]

Duplicate of #30211. Should be addressed by #30232.

[igorcferreira]

@richardlau Sorry for the duplicated issue. I failed in my search for an already open issue.