Bump @js-temporal/polyfill from 0.2.0 to 0.4.1

[dependabot]

Bumps @js-temporal/polyfill from 0.2.0 to 0.4.1.

Release notes

Sourced from @​js-temporal/polyfill's releases.

Version 0.4.1

Please see CHANGELOG.md for a summary of changes in this release.

Version 0.4.0

Please see CHANGELOG.md for a summary of changes in this release.

Thanks to everyone who contributed to this release!

• James Wright @​12wrigja
• Justin Grant @​justingrant
• Philip Nagler-Frank @​bananer
• Tiger Oakes @​NotWoods

Version 0.3.0

Please see CHANGELOG.md for a summary of changes in this release.

Thanks to everyone who contributed to this release!

• Cam Tenny @​cjtenny
• Chris Veness @​chrisveness
• Facundo Gaich @​facugaich
• James Wright @​12wrigja
• Justin Grant @​justingrant
• Ms2ger @​Ms2ger
• Philip Chimento @​ptomato
• Philip Nagler-Frank @​bananer

Changelog

Sourced from @​js-temporal/polyfill's changelog.

0.4.1

This version is a patch version enabling polyfill compatibilit with Safari versions <15.1 (October 2021 and earlier).

Bug fixes:

• Remove erroneous options from Safari's Intl.DateTimeFormat resolvedOptions bag. The underlying bug in Safari was fixed in Safari 15.1.

0.4.0

This version roughly corresponds with all the changes made to the Temporal polyfill as of the January 2022 TC39 Plenary meeting.

Breaking changes:

• Use JSBI instead of big-integer for Big Integer math operations. If your codebase does not need to polyfill BigInt, consider using the JSBI Babel plugin to transpile these operations to native BigInt.
• Reject plain date-only strings ([b733c213], see also Spec PR, proposal-temporal polyfill PR)
• Reject '-000000' as an extended year value ([670cda6b], see also Spec PR)
• Add missing branding checks for Calendar and Timezone classes to match spec changes ([670cda6b], see also Spec PR)

Bug fixes:

• Temporal class prototypes are no longer writeable ([871d28dc], see also proposal-temporal polyfill PR)
• Throw a RangeError for invalid offset strings ([d5ada8b0], see also proposal-temporal polyfill PR)
• Pad fractional second values correctly in Duration.prototype.toString() ([e046ccdf], see also Spec PR)
• Support the numberless output of Hebrew months from Intl.DateTimeFormat ([b06ac47f], see also proposal-temporal polyfill PR)
• Workaround FireFox bug with Gregory era names ([30c4d4d8], see also proposal-temporal polyfill PR)

Non-breaking changes:

• Rename public ...FromFields types ([3554d7f1])
• Add validation for hard-coded Era data in Calendar.ts ([08e84c9f])
• Improve code in Calendar.ts to handle calendar with a constant era but a variable number of months in a year ([ef8c588b])
• Add an optional calendar to PlainTime, PlainDateTime, and PlainMonthDay ([f8837367], see also Spec PR)
• Only require a year in Gregorian calendar implementations, not a full date ([02aec1c3])
• Include valueOf in the Temporal.Duration type ([b1dd7eb3])
• Expand the types allowed to be used as TimezoneLike and CalendarLike to match the spec ([9d54c646])
• Improve worse-case performance when finding Timezone transition points by over 1000X! ([e70d6324])
• Change Calendar.fields to return an Array, not an Iterable ([3145c6c4], see also Spec PR)

Other:

• Update build dependencies ([500b4c97])
• Run tests against Node 17 on CI ([db63e22a])

0.3.0

This version roughly corresponds with all the changes made to the Temporal polyfill as of the October 2021 TC39 Plenary meeting.

... (truncated)

Commits

• 32526b3 Release 0.4.1. (#148)
• 2f6e6b4 Remove erroneous options from Safari's Intl.DateTimeFormat resolvedOptions. (...
• 5df9d9f Release v0.4.0. (#143)
• 670cda6 Port recent changes from tc39/proposal-temporal. (#142)
• 3145c6c Fix Calendar.fields return type to match the spec
• f2e2658 Fix Node16 tests (port proposal-temporal/#2064)
• 281684c Fix Node14 tests broken by ICU update
• e70d632 Fix TimeZone.p.getXxxTransition() worst-case perf
• 21272b2 Restore comment about chromium issue
• 62639c8 parseFromEnUsFormat throws on unexpected input
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by jameswr, a new releaser for @​js-temporal/polyfill since your current version.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Looks like @js-temporal/polyfill is up-to-date now, so this is no longer needed.