@11ty/parse-date-strings v2.0.5

• Fix bug for a negative offset with minutes precision by @fabon-f in #3
• Add JSDoc Types by @mxdvl in #6
• Refactor getTimezoneOffset with explicit defaults by @mxdvl in #4
• Refactor getByDateTime & getParts with explicit arguments by @mxdvl in #5

Thank you @fabon-f and @mxdvl!

Milestone: https://github.com/11ty/parse-date-strings/milestone/1?closed=1
Full Changelog: v2.0.4...v2.0.5

parse-date-strings v2.0.4

• Removes some vestigial code that was no longer necessary!

Full Changelog: v2.0.3...v2.0.4

parse-date-strings v2.0.3

• Accurately fail when attempting to use more than nine digits in seconds precision

Full Changelog: v2.0.2...v2.0.3

parse-date-strings v2.0.2

• Adds support for RFC 9557 case sensitive datetime delimiter t
• Adds support for RFC 9557 datetime delimiter (space)
• Adds support for RFC 9557 ±YYYYYY six digit years

Full Changelog: v2.0.1...v2.0.2

parse-date-strings v2.0.1

• Removes some test files that snuck into the npm package

Full Changelog: v2.0.0...v2.0.1

parse-date-strings v2.0.0

• All dates supported by this library are RFC-9557 compatible (can parse with Temporal.PlainDate.from, Temporal.Instant.from, or Temporal.PlainDateTime.from) to prepare for wider Temporal API support.
  • Note that this package is not a full polyfill — not all RFC-9557 dates are supported here. Alternatives: temporal-polyfill or js-temporal/temporal-polyfill
  • Breaking: drops support for YYYY syntax
  • Breaking: drops support for YYYYMM syntax
  • Delimiters in dates (-) and times (:) are optional.
• Full test suite now compares with temporal-polyfill output

Full Changelog: v1.0.0...v2.0.0