@fr0st/datetime 7.0.0 → 8.0.1

package/Formats.md

@@ -449,27 +449,6 @@
     </tbody>
 </table>
 <p><em>* Output only</em></p>
-<p><strong>Narrow month and weekday names are output only. See the compatibility matrix below for intentionally unsupported widths.</strong></p>
+<p><strong>Narrow month and weekday names are output only. Use the token widths shown above; unsupported widths throw an error.</strong></p>
 <p><strong>Characters wrapped in <code>'</code> quotes are treated as literal text. A doubled apostrophe (<code>''</code>) represents one literal apostrophe during formatting and parsing, including inside quoted text: <code>yyyy 'o''clock'</code> → <code>2019 o'clock</code>.</strong></p>
 <p><strong>Numeric date and time fields use the active locale's numbering system during formatting and parsing, including non-BMP digits when supported by the runtime.</strong></p>
-
-## PHP `IntlDateFormatter` token-width compatibility
-
-The expected PHP behavior was recorded with PHP 8.5.9 and ICU 70.1 using the Gregorian calendar. “Equivalent” describes the pattern-width behavior; localized names can still vary with the ICU data installed in each runtime.
-
-| Tokens | Supported widths | Status and PHP behavior |
-|---|---|---|
-| `G` | All | Equivalent: widths 1–3 and 6+ are abbreviated, 4 is long, and 5 is narrow. |
-| `y`, `Y` | All | Equivalent: `yy` uses the two low-order digits; other widths set minimum numeric padding, such as `yyyyy` → `02018`. |
-| `Q`, `q` | 1–2 and 5+ | Equivalent numeric and narrow/fallback forms. Widths 3–4 are intentionally unsupported because PHP uses localized quarter forms such as `Q2` and `2nd quarter`, which JavaScript `Intl` does not expose. |
-| `M`, `L` | All for formatting; all except 5 for parsing | Equivalent: widths 3–5 are abbreviated, long, and narrow names; widths 6+ return to padded numbers, such as `MMMMMM` → `000006`. Narrow names are output only because they are not reliably unique. |
-| `w`, `W`, `d`, `D`, `F` | All | Equivalent numeric padding, such as `www` → `022` and `dddd` → `0001`. |
-| `E`, `e`, `c` | All except 6; width 5 is output only | Widths 1–5 and 7+ are equivalent. Width 6 is intentionally unsupported because PHP uses a distinct short form such as `EEEEEE` → `Fr`, which JavaScript `Intl` does not expose. Narrow names are output only because they are not reliably unique. |
-| `a` | 1–4 | Equivalent for abbreviated and long day periods. Widths 5+ are intentionally unsupported because PHP uses narrow values such as `p`, which JavaScript `Intl` does not reliably expose. |
-| `h`, `H`, `K`, `k`, `m`, `s` | All | Equivalent numeric padding. |
-| `S` | All | Supported with millisecond precision: formatting pads beyond three digits with zeroes and parsing truncates additional precision. |
-| `z` | All, output only | Equivalent width selection: widths 1–3 are short and 4+ are long. The exact name depends on runtime ICU data. |
-| `Z` | All | Equivalent: widths 1–3 are basic offsets, 4 and 6+ are localized GMT, and 5 is an extended ISO offset. |
-| `O` | 1 and 4 | Width 4 is equivalent. Width 1 uses a two-digit hour (`GMT-04`) instead of PHP’s `GMT-4`; other widths are intentionally unsupported. |
-| `V` | 2 | Equivalent IANA time-zone ID. PHP’s short ID, exemplar city, and generic location widths are intentionally unsupported. |
-| `X`, `x` | 1–5 | Equivalent ISO offset widths. Widths 6+ are intentionally unsupported. |

package/README.md

@@ -42,7 +42,7 @@ Load the bundle from your own copy or a CDN:
 <script src="https://cdn.jsdelivr.net/npm/@fr0st/datetime@latest/dist/frost-datetime.min.js"></script>
 <script>
     const date = DateTime.now({ timeZone: 'UTC' });
-    console.log(date.toISOString());
+    console.log(date.toIsoString());
 </script>
 ```
 
@@ -62,7 +62,7 @@ const nextWeek = meeting.addWeeks(1);
 nextWeek.toString();
 // Mon Mar 30 2026 09:30:00 +1000 (Australia/Brisbane)
 
-nextWeek.toISOString();
+nextWeek.toIsoString();
 // 2026-03-29T23:30:00.000+00:00
 
 nextWeek.monthName();
@@ -87,11 +87,11 @@ FrostDateTime revolves around an immutable `DateTime` class and a small set of p
 const a = DateTime.fromArray([2026, 3, 23], { timeZone: 'UTC' });
 const b = a.addDays(1);
 
-a.toISOString(); // 2026-03-23T00:00:00.000+00:00
-b.toISOString(); // 2026-03-24T00:00:00.000+00:00
+a.toIsoString(); // 2026-03-23T00:00:00.000+00:00
+b.toIsoString(); // 2026-03-24T00:00:00.000+00:00
 
 new DateTime('January 1, 2019 00:00:00', { timeZone: 'Australia/Brisbane' })
-    .toISOString();
+    .toIsoString();
 // 2018-12-31T14:00:00.000+00:00
 ```
 
@@ -154,7 +154,7 @@ A time-only `fromFormat()` pattern starts from January 1, 1970 in the requested
 DateTime.fromFormat('yyyyMMddHHmmss', '20190102123456');
 ```
 
-`fromFormat()` rejects output-only or intentionally unsupported token widths. The compatibility matrix in [Formats.md](./Formats.md#php-intldateformatter-token-width-compatibility) records the supported PHP behavior and known differences.
+`fromFormat()` rejects output-only or intentionally unsupported token widths.
 
 Format tokens are documented in [Formats.md](./Formats.md).
 
@@ -164,7 +164,7 @@ Format tokens are documented in [Formats.md](./Formats.md).
 - `toString()`: `eee MMM dd yyyy HH:mm:ss xx (VV)`
 - `toDateString()`: `eee MMM dd yyyy`
 - `toTimeString()`: `HH:mm:ss xx (VV)`
-- `toISOString()`: `yyyy-MM-dd'T'HH:mm:ss.SSSxxx` in English and UTC
+- `toIsoString()`: `yyyy-MM-dd'T'HH:mm:ss.SSSxxx` in English and UTC
 - `toJSON()`: same UTC ISO string for valid dates, `null` for invalid dates
 - `toUTCString()`: `toString()` shape in English and UTC
 
@@ -384,9 +384,9 @@ DateTime.clearDataCache();
 
 - Constructor-based parsing throws on invalid strings or unsupported time zones.
 - `fromFormat()` rejects trailing characters and marks impossible parsed dates as `isValid === false`.
-- `fromISOString()` parses the RFC 3339 / ISO-style shape used by `toISOString()`.
-- `toISOString()` always returns a UTC string regardless of the instance time zone.
-- `toJSON()` returns the same value as `toISOString()` for valid dates and `null` for invalid dates.
+- `fromISOString()` parses the RFC 3339 / ISO-style shape used by `toIsoString()`.
+- `toIsoString()` always returns a UTC string regardless of the instance time zone.
+- `toJSON()` returns the same value as `toIsoString()` for valid dates and `null` for invalid dates.
 - `withTimeZone()` keeps the same instant and changes representation.
 - `withTimeZoneOffset()` returns a fixed-offset view of the same instant.
 - A nonexistent local wall time moves forward to the next valid time, while a repeated wall time uses the later occurrence.