terminus-ui
terminus-ui copied to clipboard
chore(packages): update dependency date-fns to v3
This PR contains the following updates:
| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
| date-fns | ^2.0.1 -> ^2.0.1 || ^3.0.0 |
||||
| date-fns | 2.12.0 -> 3.0.6 |
Release Notes
date-fns/date-fns (date-fns)
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.tsfiles. 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.tsfiles. -
Added
package.jsonto 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.mtsfiles 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.mjsextension. -
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.tsfiles for more information. -
BREAKING:
constantsnow 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
Intervalarguments 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.-
areIntervalsOverlappingnormalize 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 theinclusiveoption is passed. Otherwise, and when even one of the intervals has both properties invalid, the function will always returnfalse. -
getOverlappingDaysInIntervalsnow 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. -
isWithinIntervalnow 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. -
intervalToDurationnow 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 thestepoption now also allow negative, 0, and NaN values and return reversed results if the step is negative and an empty array otherwise.
-
-
BREAKING:
intervalToDurationnow skips 0 values in the resulting duration, resulting in more compact objects with only relevant properties. -
BREAKING:
roundToNearestMinutesnow returnsInvalid Dateinstead of throwing an error whennearestTooption is less than 1 or more than 30. -
BREAKING: IE is no longer supported.
-
BREAKING: Now all functions use
Math.truncrounding method where rounding is required. The behavior is configurable on a per-function basis. -
BREAKING: Undocumented
onlyNumericoption was removed fromnnandsvlocales. 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, andeachYearOfIntervalnow accept thestepoption like most of the eachXOfInterval functions. -
A new
intervalfunction that validates interval, emulating the v2 interval functions behavior. -
differenceInXfunctions now accept options and allow setting uproundingMethodthat configures how the result is rounded.Math.truncis the default method.
Configuration
📅 Schedule: Branch creation - "before 4am on the first day of the month" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
â™» Rebasing: Never, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
- [ ] If you want to rebase/retry this PR, check this box
This PR has been generated by Mend Renovate. View repository job log here.