⚙ Compilation target
ESNext
⚙ Library
ESNext
Missing / Incorrect Definition
|
toLocaleString(locales?: Intl.LocalesArgument, options?: Intl.DateTimeFormatOptions): string; |
Sample Code
TypeScript allows the following code, when it should not.
Temporal.Now.zonedDateTimeISO("America/Chicago").toLocaleString(undefined, { timeZone: "Europe/Berlin" });Result
| Engine |
Error |
| JavaScriptCore |
TypeError: ZonedDateTime.toLocaleString does not accept a timeZone option; the ZonedDateTime's time zone is used |
| SpiderMonkey |
TypeError: can't set option timeZone when Temporal.ZonedDateTime.toLocaleString is used |
| V8 |
TypeError: Invalid time zone specified: America/Chicago |
Documentation Link
According to MDN:
The timeZone option must not be provided, as it is automatically set to be the date-time's timeZoneId.
The type definitions should be changed to
declare namespace Temporal {
// ...
interface ZonedDateTimeToLocaleStringOptions extends Omit<Intl.DateTimeFormatOptions, "timeZone"> {}
// ...
interface ZonedDateTime {
// ...
toLocaleString(locales?: Intl.LocalesArgument, options?: ZonedDateTimeToLocaleStringOptions): string;
}
}
⚙ Compilation target
ESNext
⚙ Library
ESNext
Missing / Incorrect Definition
TypeScript/tsc/internal/bundled/libs/lib.esnext.temporal.d.ts
Line 320 in 0b832e1
Sample Code
TypeScript allows the following code, when it should not.
Result
TypeError: ZonedDateTime.toLocaleString does not accept a timeZone option; the ZonedDateTime's time zone is usedTypeError: can't set option timeZone when Temporal.ZonedDateTime.toLocaleString is usedTypeError: Invalid time zone specified: America/ChicagoDocumentation Link
According to MDN:
The type definitions should be changed to