-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update dependency date-fns to v3 #1059
Open
renovate
wants to merge
1
commit into
develop
Choose a base branch
from
renovate/date-fns-3.x
base: develop
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
renovate
bot
force-pushed
the
renovate/date-fns-3.x
branch
5 times, most recently
from
December 29, 2023 20:07
30f03d5
to
29ce4a3
Compare
renovate
bot
force-pushed
the
renovate/date-fns-3.x
branch
5 times, most recently
from
January 5, 2024 22:20
7555679
to
0c33c85
Compare
renovate
bot
force-pushed
the
renovate/date-fns-3.x
branch
7 times, most recently
from
January 13, 2024 06:57
91be0c0
to
b43c69d
Compare
renovate
bot
force-pushed
the
renovate/date-fns-3.x
branch
7 times, most recently
from
January 20, 2024 08:03
6f0a11c
to
166a780
Compare
renovate
bot
force-pushed
the
renovate/date-fns-3.x
branch
3 times, most recently
from
January 26, 2024 23:03
fe4ed9c
to
3007b46
Compare
renovate
bot
force-pushed
the
renovate/date-fns-3.x
branch
4 times, most recently
from
February 17, 2024 01:10
2768a4c
to
53ea61e
Compare
renovate
bot
force-pushed
the
renovate/date-fns-3.x
branch
4 times, most recently
from
February 23, 2024 19:12
1ac7e7b
to
a6abfb0
Compare
renovate
bot
force-pushed
the
renovate/date-fns-3.x
branch
from
March 2, 2024 13:37
a6abfb0
to
3cbd682
Compare
renovate
bot
force-pushed
the
renovate/date-fns-3.x
branch
4 times, most recently
from
March 18, 2024 02:25
2a493fd
to
fa4edbb
Compare
renovate
bot
force-pushed
the
renovate/date-fns-3.x
branch
from
March 22, 2024 22:19
fa4edbb
to
9bc1331
Compare
renovate
bot
force-pushed
the
renovate/date-fns-3.x
branch
from
April 5, 2024 23:23
9bc1331
to
25959ad
Compare
renovate
bot
force-pushed
the
renovate/date-fns-3.x
branch
2 times, most recently
from
May 24, 2024 18:04
3379e9d
to
accc91b
Compare
renovate
bot
force-pushed
the
renovate/date-fns-3.x
branch
from
June 7, 2024 18:39
accc91b
to
f847a39
Compare
renovate
bot
force-pushed
the
renovate/date-fns-3.x
branch
2 times, most recently
from
June 14, 2024 22:51
88f8ea3
to
d94b123
Compare
renovate
bot
force-pushed
the
renovate/date-fns-3.x
branch
from
June 21, 2024 21:39
d94b123
to
05f5adb
Compare
renovate
bot
force-pushed
the
renovate/date-fns-3.x
branch
from
June 22, 2024 00:07
05f5adb
to
2e8d620
Compare
renovate
bot
changed the title
Update dependency date-fns to v3
Update dependency date-fns to v3 - autoclosed
Dec 8, 2024
renovate
bot
changed the title
Update dependency date-fns to v3 - autoclosed
Update dependency date-fns to v3
Dec 13, 2024
renovate
bot
force-pushed
the
renovate/date-fns-3.x
branch
from
December 13, 2024 22:01
dfe1774
to
2e8d620
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR contains the following updates:
2.30.0
->3.6.0
Release Notes
date-fns/date-fns (date-fns)
v3.6.0
Compare Source
On this release worked @kossnocorp and @world1dan. Also, thanks to @seated for sponsoring me.
Fixed
formatDistance
.Added
v3.5.0
Compare Source
Kudos to @fturmel, @kossnocorp, @makstyle119, @tan75, @marcreichel, @tareknatsheh and @audunru for working on the release. Also, thanks to @seated for sponsoring me.
Fixed
Fixed functions that use current date internally and made them work with date extensions like
UTCDate
.Fixed
daysToWeeks
returning negative 0.Fixed German grammar for the "half a minute" string.
Added
constructNow
function that creates the current date using the passed reference date's constructor.v3.4.0
Compare Source
Kudos to @kossnocorp, @sakamossan and @Revan99 for working on the release. Also thanks to @seated for sponsoring me.
Added
Added
roundToNearestHours
function.Added Central Kurdish (
ckb
) locale.v3.3.1
Compare Source
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
Compare Source
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
format
aliasformatDate
with correspondingFormatDateOptions
interface.v3.2.0
Compare Source
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)Fixed inconsistent behavior of
roundToNearestMinutes
.Added
format
,lightFormat
, andparse
internals that enable 3rd-parties to consume those.v3.1.0
Compare Source
This release is brought to you by @kossnocorp, @makstyle119 and @dmgawel.
Fixed
Added
Added
yearsToDays
function.Added warning about using protected tokens like
Y
orD
without passing a corresponding option. See #2950.v3.0.6
Compare Source
On this release worked @imwh0im, @jamcry and @tyrw.
Fixed
areIntervalsOverlapping
caused by incorrect sorting (#3614)v3.0.5
Compare Source
This release is brought to you by @goku4199.
Fixed
toDate
not processing string arguments properlyv3.0.4
Compare Source
This release is brought to you by @kossnocorp.
Fixed
v3.0.3
Compare Source
Fixed
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
Compare Source
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
Compare Source
Fixed
d.mts
files exporting only types.v3.0.0
Compare Source
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
📅 Schedule: Branch creation - "every weekend" in timezone Asia/Tokyo, Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.