Update dependency date-fns to v3
This MR contains the following updates:
Package | Type | Update | Change |
---|---|---|---|
date-fns | dependencies | major | ^2.29.0 -> ^3.0.0 |
Release Notes
date-fns/date-fns (date-fns)
v3.3.1
Kudos to @kossnocorp and @fturmel for working on the release.
Fixed
-
Fixed DST issue in
getOverlappingDaysInIntervals
, resulting in an inconsistent number of days returned for intervals starting and ending in different DST periods. -
Fixed functions incorrectly using
trunc
instead ofround
. The bug was introduced in v3.3.0. The affected functions:differenceInCalendarDays
,differenceInCalendarISOWeeks
,differenceInCalendarWeeks
,getISOWeek
,getWeek
, andgetISOWeeksInYear
.
v3.3.0
On this release worked @kossnocorp, @TheKvikk, @fturmel and @ckcherry23.
Fixed
-
Fixed the bug in
getOverlappingDaysInIntervals
caused by incorrect sorting of interval components that led to 0 for timestamps of different lengths. -
Fixed bugs when working with negative numbers caused by using
Math.floor
(-1.1
→-2
) instead ofMath.trunc
(-1.1
→-1
). Most of the conversion functions (i.e.,hoursToMinutes
) were affected when passing some negative fractional input. Also, some other functions that could be possibly affected by unfortunate timezone/date combinations were fixed.The functions that were affected:
format
,parse
,getUnixTime
,daysToWeeks
,hoursToMilliseconds
,hoursToMinutes
,hoursToSeconds
,milliseconds
,minutesToMilliseconds
,millisecondsToMinutes
,monthsToYears
,millisecondsToHours
,millisecondsToSeconds
,minutesToHours
,minutesToSeconds
,yearsToQuarters
,yearsToMonths
,yearsToDays
,weeksToDays
,secondsToMinutes
,secondsToHours
,quartersToYears
,quartersToMonths
andmonthsToQuarters
. -
Fixed the Czech locale's
formatDistance
to include1
informatDistance
. -
Fixed
differenceInSeconds
and other functions relying on rounding options that can produce a negative 0. -
Added a preprocessor to the locales API, enabling fixing a long-standing bug in the French locale. (#1391)
-
Added missing
yearsToDays
to the FP submodule. -
Made functions using rounding methods always return
0
instead of-0
.
Added
v3.2.0
This release is brought to you by @kossnocorp, @fturmel, @grossbart, @MelvinVermeer, and @jcarstairs-scottlogic.
Fixed
-
Fixed types compatability with Lodash's
flow
and fp-ts'spipe
. (#3641)
Added
- Added exports of
format
,lightFormat
, andparse
internals that enable 3rd-parties to consume those.
v3.1.0
This release is brought to you by @kossnocorp, @makstyle119 and @dmgawel.
Fixed
Added
-
Added warning about using protected tokens like
Y
orD
without passing a corresponding option. See #2950.
v3.0.6
On this release worked @imwh0im, @jamcry and @tyrw.
Fixed
v3.0.5
This release is brought to you by @goku4199.
Fixed
v3.0.4
This release is brought to you by @kossnocorp.
Fixed
- Fixed isWithinInterval bug caused by incorrectly sorting dates (#3623).
v3.0.3
Fixed
- Rolled back pointing ESM types to the same
d.ts
files. Instead now it copies the content to avoid the Masquerading as CJS problem reported by "Are the types wrong?".
v3.0.2
Fixed
-
Fixed yet another issue caused by ESM types by pointing to the same
d.ts
files. -
Added
package.json
to exports to provide access to tooling. -
Fixed TypeScript 5.4 build break by using the latest type names.
v3.0.1
Fixed
-
Fixed an error in certain environments caused by
d.mts
files exporting only types.
v3.0.0
Changed
-
BREAKING: date-fns is now a dual-package with the support of both ESM and CommonJS. The files exports are now explicitly in the
package.json
. The ESM files now have.mjs
extension. -
BREAKING: The package now has a flat structure, meaning functions are now named
node_modules/date-fns/add.mjs
, locales arenode_modules/date-fns/locale/enUS.mjs
, etc. -
BREAKING: Now all file content’s exported via named exports instead of
export default
, which will require change direct imports i.e.const addDays = require(‘date-fns/addDays’)
toconst { addDays } = require(‘date-fns/addDays’)
. -
BREAKING: TypeScript types are now completely rewritten, check out the
d.ts
files for more information. -
BREAKING:
constants
now is not exported via the index, so to import one useimport { daysInYear } from "date-fns/constants";
. It improves compatibility with setups that modularize imports like Next.js. -
BREAKING: Functions now don’t check the number of passed arguments, delegating this task to type checkers. The functions are now slimmer because of this.
-
BREAKING The arguments are not explicitly converted to the target types. Instead, they are passed as is, delegating this task to type checkers.
-
BREAKING: Functions that accept
Interval
arguments now do not throw an error if the start is before the end and handle it as a negative interval. If one of the properties in anInvalid Date
, these functions also do not throw and handle them as invalid intervals.-
areIntervalsOverlapping
normalize intervals before comparison, so{ start: a, end: b }
is practically equivalent to{ start: b, end: a }
. When comparing intervals with one of the properties beingInvalid Date
, the function will return false unless the others are valid and equal, given theinclusive
option is passed. Otherwise, and when even one of the intervals has both properties invalid, the function will always returnfalse
. -
getOverlappingDaysInIntervals
now normalizes intervals before comparison, so{ start: a, end: b }
is practically equivalent to{ start: b, end: a }
. If any of the intervals’ properties is anInvalid Date
, the function will always return 0. -
isWithinInterval
now normalizes intervals before comparison, so{ start: a, end: b }
is practically equivalent to{ start: b, end: a }
. If any of the intervals’ properties is anInvalid Date
, the function will always return false. -
intervalToDuration
now returns negative durations for negative intervals. If one or both of the interval properties are invalid, the function will return an empty object. -
The eachXOfInterval functions (
eachDayOfInterval
,eachHourOfInterval
,eachMinuteOfInterval
,eachMonthOfInterval
,eachWeekendOfInterval
,eachWeekendOfMonth
,eachWeekendOfYear
,eachWeekOfInterval
,eachYearOfInterval
) now return a reversed array if the passed interval’s start is after the end. Invalid properties will result in an empty array. Functions that accept thestep
option now also allow negative, 0, and NaN values and return reversed results if the step is negative and an empty array otherwise.
-
-
BREAKING:
intervalToDuration
now skips 0 values in the resulting duration, resulting in more compact objects with only relevant properties. -
BREAKING:
roundToNearestMinutes
now returnsInvalid Date
instead of throwing an error whennearestTo
option is less than 1 or more than 30. -
BREAKING: IE is no longer supported.
-
BREAKING: Now all functions use
Math.trunc
rounding method where rounding is required. The behavior is configurable on a per-function basis. -
BREAKING: Undocumented
onlyNumeric
option was removed fromnn
andsv
locales. If you relied on it, please contact me. -
BREAKING: Flow is not supported anymore. If you relied on it, please contact me.
-
BREAKING: The locales now use regular functions instead of the UTC version, which should not break any code unless you used locales directly.
Added
-
All functions that accept date arguments now also accept strings.
-
All functions now export options interfaces.
-
Now functions allow passing custom Date extensions like UTCDate. They will detect and use the arguments constructor to generate the result of the same class.
-
eachMonthOfInterval
,eachQuarterOfInterval
,eachWeekOfInterval
, andeachYearOfInterval
now accept thestep
option like most of the eachXOfInterval functions. -
A new
interval
function that validates interval, emulating the v2 interval functions behavior. -
differenceInX
functions now accept options and allow setting uproundingMethod
that configures how the result is rounded.Math.trunc
is the default method.
Configuration
-
If you want to rebase/retry this MR, check this box
This MR has been generated by Renovate Bot.