toLocaleTimeString returns invalid time when using 24hr time format

[michelnev]

Version

v20.9.0

Platform

FreeBSD freebsd 13.2-RELEASE-p4 FreeBSD 13.2-RELEASE-p4 GENERIC amd64

Subsystem

No response

What steps will reproduce the bug?

I tested on Linux as well in version v18.17.1 with the same result. Within node, simply execute the following script:

const event = new Date('2020-04-20T16:40:13.000Z');
console.log(event.toLocaleTimeString('en-US', { timeZone: 'Asia/Taipei', hour12: false}));

How often does it reproduce? Is there a required condition?

100% for the scenario described.

What is the expected behavior? Why is that the expected behavior?

Expect to see the following output:
00:40:13

What do you see instead?

Saw the following output on multiple host systems:
24:40:13

Additional information

No response

[richardlau]

You'll probably need to specify hourCycle: 'h23'. See #36219.

[silvenon]

The recommended option works, but it steers away from the way that browsers implement this. Also, this works as expected with just hour12: false in Node v22, can we expect it to be fixed in v20?