- conformance to latest spec (May 2024)
- fix: Chrome on Android reporting wrong era for islamic calendars (#39)
- fix: Bug with eras on Firefox 96 - 105 (https://bugzilla.mozilla.org/show_bug.cgi?id=1752253)
- conformance to latest spec (Apr 2024)
- fix: Typescript error when using CommonJS module outputs (#35)
- fix: PlainTime.toString() throws error with SWC minifier (#36)
- fix: temporal-spec types updated for weekOfYear/yearOfWeek
- fix: more readable error message when no valid fields specified (#30)
- fix: more readable error message when unit is out of range
- fix: non-iso/gregory calendars dayOfYear/weekOfYear off-by-one
- conformance to latest spec
- yearOfWeek/weekOfYear should return undefined for non-iso/gregory calendars
- updates to since/until algorithm
- more validation of custom timeZones' returned instants
- more validation of Duration units, max values
- prevent legacy ICU time zone IDs
- don't normalize the islamicc calenadar name to islamic-civil
- fix: when importing
'temporal-polyfill'
or'temporal-polyfill/impl'
, the symbolDateTimeFormat
is exported when in factIntl
should be exported according to thetemporal-spec
package. (#28) Potentially BREAKING CHANGE for vanilla JS users importingDateTimeFormat
. - fix: closed off potential attack vector for ReDoS attacks on regular expressions that parse ISO datetime strings (76a6aca)
- fix:
dayOfWeek
/yearOfWeek
/weekOfYear
incorrectly using local time (#26, #27) - fix: Compliant string-level normalization of time zone IDs (mentioned in #3)
- fix:
DateTimeFormat
constructor cannot be invoked withoutnew
(#25) - fix:
DateTimeFormat::format
correctly implemented as bound getter - fix:
Duration::toLocaleString
falls back totoString
- feature: better tree-shakability for ESM
- Updated with latest test262 conformance tests (Nov 2023) (#3). All tests passing barring intentional deviations from spec, documented in README.
- Breaking changes include all those mentioned here and normative changes introduced between May 2023 - Nov 2023, most notably changes to "user-visible operations".
- Size of minified+gzipped bundle increased from 17.3 kB -> 20.0 kB due to stricter compliance with latest spec.
- In NPM directory, all files are now top-level as opposed to within
dist/
. Thus, the jsDelivr URL has changed. - Fixed bugs: #9, #12, #13, #21
- Improved README content, including comparison with @js-temporal (#22)
- Renamed github repo to fullcalendar/temporal-polyfill
- fix: upgrade temporal-spec, which is now compatible with moduleResolution:node16 (#17 cont'd)
- fix: don't fallback to native Temporal implementation for ponyfill (#19 cont'd)
- fix: Support TypeScript 4.7 moduleResolution:node16 (#17)
- fix: Avoiding fallback to native Temporal implementation (#19)
- Support environments without BigInt. See browser version matrix in README.
- Fixed TypeScript syntax error in
temporal-spec/index.d.ts
(#10) - Fixed missing .d.ts files for environments that don't support export maps.
- BREAKING: side-effect-free entrypoint now exports named exports instead of default
Temporal
- No longer works:
import Temporal from 'temporal-polyfill'
- Works:
import { Temporal } from 'temporal-polyfill'
- Allows access to
Intl
side-effect-free export
- No longer works:
- Uses types created by TC39 Committee
- Improved spec-compliance. Passes all tests from @js-temporal/polyfill repo.
- Intl.DateTimeFormat correctly polyfilled to customize output based on Temporal type
- fixes to TimeZone object
- improved support for non-ISO calendars
- fixed
Now
methods returning wrong results (#5)