temporal-polyfill-lite 0.3.4 → 0.3.6

package/CHANGELOG.md

@@ -5,6 +5,19 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## 0.3.6 (2026-05-07)
+
+### Fixed
+
+- Stop implement `formatRange` and `formatRangeToParts` methods to `Intl.DateTimeFormat` on legacy browsers without support for these methods, which makes feature detection of range formatting methods work correctly ([#32](https://github.com/fabon-f/temporal-polyfill-lite/pull/32))
+
+## 0.3.5 (2026-04-20)
+
+### Fixed
+
+- Fix wrong order of observable operations for options object in `Intl.DateTimeFormat` constructor ([#28](https://github.com/fabon-f/temporal-polyfill-lite/pull/28))
+- Fix types of `Intl` when the polyfill is used as a ponyfill ([#29](https://github.com/fabon-f/temporal-polyfill-lite/pull/29))
+
 ## 0.3.4 (2026-04-14)
 
 ### Fixed

package/README.md

@@ -46,6 +46,12 @@ The polyfill works in browsers after September 2020 by default (e.g. Safari 14).
 
 This polyfill doesn't internally rely on `bigint`, thus you can support older browsers by transpiling and injecting polyfills (e.g. it relies on `globalThis` which is baseline since January 2020). However, if you use APIs accepting or returning `bigint`, `bigint` support is required.
 
+## TypeScript configuration
+
+This polyfill provides type definitions out of the box (You don't need `@types/*`).
+
+This package is ESM-only, so you have to set [`module`](https://www.typescriptlang.org/tsconfig/#module) and [`moduleResolution`](https://www.typescriptlang.org/tsconfig/#moduleResolution) correctly. It also uses the [`exports` field](https://nodejs.org/api/packages.html#exports) in `package.json`, so you should not set the [`resolvePackageJsonExports`](https://www.typescriptlang.org/tsconfig/#resolvePackageJsonExports) option to `false` in your `tsconfig.json`. Otherwise the type resolution will fail.
+
 ## Spec compliance
 
 It supports the latest spec with few intentional deviations (see `tests/expectedFailures` directory for details).

package/dist/calendars/index.d.ts

@@ -591,19 +591,19 @@ export namespace Intl {
 	}
 }
 
-export const Intl: {
+export const Intl: typeof globalThis.Intl & {
 	DateTimeFormat: {
 		new (
-			locales?: string | string[],
+			locales?: globalThis.Intl.LocalesArgument,
 			options?: globalThis.Intl.DateTimeFormatOptions,
 		): Intl.DateTimeFormat;
 		(
-			locales?: string | string[],
+			locales?: globalThis.Intl.LocalesArgument,
 			options?: globalThis.Intl.DateTimeFormatOptions,
 		): Intl.DateTimeFormat;
 
 		supportedLocalesOf(
-			locales: string | string[],
+			locales: globalThis.Intl.LocalesArgument,
 			options?: globalThis.Intl.DateTimeFormatOptions,
 		): string[];
 	};

package/dist/calendars/index.js

@@ -1,2 +1,2 @@
-import { i as a, r as s, t as r } from "./src-BRD2b69b.js";
+import { i as a, r as s, t as r } from "./src-B3jme83H.js";
 export { s as Intl, r as Temporal, a as toTemporalInstant };

package/dist/calendars/shim.js

@@ -4,5 +4,5 @@ function install(s) {
 function setSystemTimeZoneIdCacheTtl(t) {
 	s(t);
 }
-import { a as t, i as a, n as s, r as e, t as l } from "./src-BRD2b69b.js";
+import { a as t, i as a, n as s, r as e, t as l } from "./src-B3jme83H.js";
 export { install, setSystemTimeZoneIdCacheTtl };