[chore] Upgrade date-fns to v4
#7633
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Builds on #7632 (upgrade to date-fns v3), related to #6744
Summary
Upgrades
date-fnsfrom v3.6.0 to v4.1.0 and migrates from the third-partydate-fns-tzpackage to the official@date-fns/tzpackage with first-class timezone support.Changes
Package Updates
date-fns^3.6.0 → ^4.1.0, removeddate-fns-tz, added@date-fns/tz^1.2.0date-fns^3.6.0 → ^4.1.0date-fns^3.6.0 → ^4.1.0Migration to
@date-fns/tzReplaced the third-party
date-fns-tzpackage with the official@date-fns/tzpackage, which provides first-class timezone support in date-fns v4.1. Timezone Formatting
2. Timezone Offset Calculation
The API changed from returning milliseconds to returning minutes:
3. Timezone Conversion Functions
Reimplemented
convertLocalDateToTimezoneTimeandconvertDateToLocalEquivalentOfTimezoneTimeusingtzOffsetinstead of toZonedTime/fromZonedTime:Breaking Changes
None for consumers of
@blueprintjs/datetime. All changes are internal implementation details. The public API remains unchanged.Documentation