+
+ | Package |
+
+ temporal-polyfill
+ |
+
+ @js-temporal/polyfill
+ |
+
+
+ | Repo |
+
+
+ fullcalendar/temporal-polyfill
+
+ |
+
+
+ js-temporal/temporal-polyfill
+
+ |
+
+
+ | Creators |
+ FullCalendar lead dev arshaw |
+ Champions of the Temporal proposal |
+
+
+ | Minified+gzip size ✝ |
+ 20.0 kB |
+ 43.2 kB (+116%) |
+
+
+ | Minified-only size ✝ |
+ 58.7 kB |
+ 206.0 kB (+251%) |
+
+
+ | Spec compliance |
+
+ Strict compliance for common API.
+ Relaxed compliance for subclassing
built-in types.
+ |
+
+ Strict compliance for entire API.
+ |
+
+
+ | Spec date |
+
+ Nov 2023 (latest)
+ |
+
+ May 2023
+ |
+
+
+ | BigInt Approach |
+ Internally avoids BigInt operations altogether |
+ Internally relies on JSBI |
+
+
+ | Global usage in ESM |
+
+ import 'temporal-polyfill/global'
+ |
+ Not currently possible |
+
+
+
+✝ Compares [global.min.js](https://cdn.jsdelivr.net/npm/temporal-polyfill@0.2.0/global.min.js) with [index.esm.js](https://cdn.jsdelivr.net/npm/@js-temporal/polyfill@0.4.4/dist/index.esm.js), which are similarly transpiled.
+
+
+## Spec Compliance
+
+All calendar systems (ex: `chinese`, `persian`) and time zones are supported.
+
+Compliance with the latest version of the Temporal spec (Nov 2023) is near-perfect with the following intentional deviations:
+
+- `Duration::toString` does not display units greater than `Number.MAX_SAFE_INTEGER` according to spec. Precision is chosen differently.
+- *Custom implementations* of Calendars and TimeZones are queried differently. Only affects those subclassing built-in classes, which is extremely rare. See the CALLING entries in the [test-ignore file](https://github.com/fullcalendar/temporal/blob/main/packages/temporal-polyfill/scripts/test-config/expected-failures.txt).
+- There are believed to be 3 bugs in the Temporal spec itself, one of which [has been filed](https://github.com/tc39/proposal-temporal/issues/2742). See SPEC-BUG entries in the [test-ignore file](https://github.com/fullcalendar/temporal/blob/main/packages/temporal-polyfill/scripts/test-config/expected-failures.txt).
+- Canonicalization of time zone IDs is simplified, leveraging the built-in `Intl` API.
+- `Intl.DateTimeFormat` has not been polyfilled to accept number-offset values for the `timeZone` option.
+- Method descriptors and `Function::length` are not strictly compliant due to ES-related space-saving techniques.
+
+The [Official ECMAScript Conformance Test Suite](https://github.com/tc39/test262) has:
+
+- 6811 *total* Temporal-related test files
+- 6138 *passed* by `temporal-polyfill`
+- 495 *ignored* due to superficial method descriptor compliance
+- 178 *ignored* due to other aforementioned intentional deviations
+
+
+## Browser Support
+
+
+ | ❌ Avoid microseconds/nanoseconds |
+ ✅ Use milliseconds instead |
+
+
+ instant.epochMicroseconds |
+ instant.epochMilliseconds |
+
+
+ instant.epochNanoseconds |
+ instant.epochMilliseconds |
+
+
+ Temporal.Instant.fromEpochMicroseconds(micro) |
+ Temporal.Instant.fromEpochMilliseconds(milli) |
+
+
+ Temporal.Instant.fromEpochNanoseconds(nano) |
+ Temporal.Instant.fromEpochMilliseconds(milli) |
+
+
+ new Temporal.Instant(nano) |
+ Temporal.Instant.fromEpochMilliseconds(milli) |
+
+
+ zonedDateTime.epochMicroseconds |
+ zonedDateTime.epochMilliseconds |
+
+
+ zonedDateTime.epochNanoseconds |
+ zonedDateTime.epochMilliseconds |
+
+
+
+ new Temporal.ZonedDateTime(nano, tz, cal)
+ |
+
+ Temporal.Instant.fromEpochMilliseconds(milli)
+ .toZonedDateTimeISO() // or toZonedDateTime
+ |
+
+
+
+## Tree-shakeable API
+
+🚧 Coming Soon
+
+For library authors and other devs who are hyper-concerned about bundle size, `temporal-polyfill` will be providing an alternate API designed for tree-shaking.
+
+```js
+import * as ZonedDateTime from 'temporal-polyfill/fns/zoneddatetime'
+
+const zdt = ZonedDateTime.from({ year: 2024, month: 1, day: 1 })
+const s = ZonedDateTime.toString(zdt) // not how you normally call a method!
+```
diff --git a/babel.config.cjs b/babel.config.cjs
deleted file mode 100644
index c6279a40..00000000
--- a/babel.config.cjs
+++ /dev/null
@@ -1,9 +0,0 @@
-// For Jest. Individual packages extend this config
-// TODO: when running test in "built-mode", don't do any babel transforming
-
-module.exports = {
- presets: [
- ['@babel/preset-env', { targets: { node: 'current' } }],
- '@babel/preset-typescript',
- ],
-}
diff --git a/scripts/config/eslint.cjs b/eslint.base.cjs
similarity index 100%
rename from scripts/config/eslint.cjs
rename to eslint.base.cjs
diff --git a/jest.config.base.cjs b/jest.config.base.cjs
deleted file mode 100644
index 11d8343d..00000000
--- a/jest.config.base.cjs
+++ /dev/null
@@ -1,8 +0,0 @@
-// Only contains simple config that does not reference third-party packages
-
-process.env.TZ = 'America/New_York'
-
-module.exports = {
- // timers: 'modern',
- // verbose: true,
-}
diff --git a/jest.config.cjs b/jest.config.cjs
deleted file mode 100644
index 46fca186..00000000
--- a/jest.config.cjs
+++ /dev/null
@@ -1,12 +0,0 @@
-const base = require('./jest.config.base.cjs')
-
-module.exports = {
- ...base,
- projects: [
- '