You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This release revisits the approach to CDN usage and introduces a new package, @date-fns/cdn and deprecates the date-fns CDN scripts. It allowed reducing the zipped package size from 5.83 MB down to 3.96 MB without introducing any breaking changes.
In v5.0.0-alpha.0 where CDN scripts are completely removed from date-fns the change is more significant and brings the zipped package size down to 2.89 MB.
It is just the first step in optimizing the package size. Expect further size reduction in the future v4 and v5 versions.
Changed
DEPRECATED: The date-fns CDN scripts are now deprecated and will be removed in the next major release. Please switch to the new @date-fns/cdn package for CDN usage.
Removed CDN source maps to reduce the package size. If you rely on them, please switch to the new @date-fns/cdn package that still includes them.
Fixed internal constructFrom throwing an exception on null arguments. While null isn't allowed, the functions should rather return Invalid Date or NaN in such cases. See #3885.
Added
Added missing time zone support to format, formatISO, formatISO9075, formatRelative and formatRFC3339. See #3886.
I have great news! First, ten years after its release, date-fns finally gets first-class time zone support.
Another great news is that there aren't many breaking changes in this release. All of them are type-related and will affect only those explicitly using internal date-fns types. Finally, it has been less than a year since the last major release, which is an improvement over the previous four years between v2 and v3. I plan on keeping the pace and minimizing breaking changes moving forward.
Added time zones support via @date-fns/tz's TZDate class and tz helper function. See its README for the details about the API.
All relevant functions now accept the context in option, which allows to specify the time zone to make the calculations in. If the function also returns a date, it will be in the specified time zone:
In the example, addDays will get the current date and time in Singapore and add 5 days to it. startOfDay will inherit the date type and return the start of the day in Singapore.
Changed
The function arguments, as well as Interval's start and end, now can be of different types, allowing you to mix UTCDate, TZDate, Date, and other extensions, as well as primitives (strings and numbers).
The functions will normalize these values, make calculations, and return the result in the same type, preventing any bugs caused by the discrepancy. If passed, the type will be inferred from the context in option or the first encountered argument object type. The Interval's start and end will be considered separately, starting from start.
In the given example, the result will be in the TZDate as the first argument is a number, and the start takes precedence over the end.
BREAKING: This release contains a bunch of types changes that should not affect the library's expected usage. The changes are primarily internal and nuanced, so rather than listing them here, I recommend you running the type checker after the upgrade. If there are unfixable problems, please open an issue.
BREAKING: The package now is ESM-first. The CommonJS is still support and It should not affect most users, but it might break in certains environments. If you encounter any issues, please report them.
Fixed
Fixed CDN build compatibility with jQuery and other tools that expose $ by properly wrapping the code in an IIFE.
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 of round. The bug was introduced in v3.3.0. The affected functions: differenceInCalendarDays, differenceInCalendarISOWeeks, differenceInCalendarWeeks, getISOWeek, getWeek, and getISOWeeksInYear.
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 of Math.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 and monthsToQuarters.
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?".
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 are node_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’) to const { 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 use import { 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 an Invalid 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 being Invalid Date, the function will return false unless the others are valid and equal, given the inclusive option is passed. Otherwise, and when even one of the intervals has both properties invalid, the function will always return false.
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 an Invalid 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 an Invalid 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 the step 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 returns Invalid Date instead of throwing an error when nearestTo 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 from nn and sv 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, and eachYearOfInterval now accept the step 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 up roundingMethod that configures how the result is rounded. Math.trunc is the default method.
Fixed increased build size after enabling compatibility with older browsers in the previous release. This was done by adding @babel/runtime as a dependency. See more details.
Next steps: Take a moment to review the security alert above. Review
the linked package source code to understand the potential risk. Ensure the
package is not malicious before proceeding. If you're unsure how to proceed,
reach out to your security team or ask the Socket team for help at
support@socket.dev.
Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.
Mark the package as acceptable risk. To ignore this alert only
in this pull request, reply with the comment
@SocketSecurity ignore npm/babel-traverse@6.26.0. You can
also ignore all packages with @SocketSecurity ignore-all.
To ignore an alert for all future pull requests, use Socket's Dashboard to
change the triage state of this alert.
Warn
Critical CVE: npm json-schema is vulnerable to Prototype Pollution
Next steps: Take a moment to review the security alert above. Review
the linked package source code to understand the potential risk. Ensure the
package is not malicious before proceeding. If you're unsure how to proceed,
reach out to your security team or ask the Socket team for help at
support@socket.dev.
Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.
Mark the package as acceptable risk. To ignore this alert only
in this pull request, reply with the comment
@SocketSecurity ignore npm/json-schema@0.2.3. You can
also ignore all packages with @SocketSecurity ignore-all.
To ignore an alert for all future pull requests, use Socket's Dashboard to
change the triage state of this alert.
Next steps: Take a moment to review the security alert above. Review
the linked package source code to understand the potential risk. Ensure the
package is not malicious before proceeding. If you're unsure how to proceed,
reach out to your security team or ask the Socket team for help at
support@socket.dev.
Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.
Mark the package as acceptable risk. To ignore this alert only
in this pull request, reply with the comment
@SocketSecurity ignore npm/minimist@1.2.5. You can
also ignore all packages with @SocketSecurity ignore-all.
To ignore an alert for all future pull requests, use Socket's Dashboard to
change the triage state of this alert.
Warn
Critical CVE: npm pbkdf2 returns predictable uninitialized/zero-filled memory for non-normalized or unimplemented algos
Next steps: Take a moment to review the security alert above. Review
the linked package source code to understand the potential risk. Ensure the
package is not malicious before proceeding. If you're unsure how to proceed,
reach out to your security team or ask the Socket team for help at
support@socket.dev.
Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.
Mark the package as acceptable risk. To ignore this alert only
in this pull request, reply with the comment
@SocketSecurity ignore npm/pbkdf2@3.1.2. You can
also ignore all packages with @SocketSecurity ignore-all.
To ignore an alert for all future pull requests, use Socket's Dashboard to
change the triage state of this alert.
Next steps: Take a moment to review the security alert above. Review
the linked package source code to understand the potential risk. Ensure the
package is not malicious before proceeding. If you're unsure how to proceed,
reach out to your security team or ask the Socket team for help at
support@socket.dev.
Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.
Mark the package as acceptable risk. To ignore this alert only
in this pull request, reply with the comment
@SocketSecurity ignore npm/pbkdf2@3.1.2. You can
also ignore all packages with @SocketSecurity ignore-all.
To ignore an alert for all future pull requests, use Socket's Dashboard to
change the triage state of this alert.
Warn
Critical CVE: Improper Neutralization of Special Elements used in a Command in Shell-quote
Next steps: Take a moment to review the security alert above. Review
the linked package source code to understand the potential risk. Ensure the
package is not malicious before proceeding. If you're unsure how to proceed,
reach out to your security team or ask the Socket team for help at
support@socket.dev.
Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.
Mark the package as acceptable risk. To ignore this alert only
in this pull request, reply with the comment
@SocketSecurity ignore npm/shell-quote@1.7.2. You can
also ignore all packages with @SocketSecurity ignore-all.
To ignore an alert for all future pull requests, use Socket's Dashboard to
change the triage state of this alert.
Warn
Obfuscated code: npm buffer is 96.0% likely obfuscated
Next steps: Take a moment to review the security alert above. Review
the linked package source code to understand the potential risk. Ensure the
package is not malicious before proceeding. If you're unsure how to proceed,
reach out to your security team or ask the Socket team for help at
support@socket.dev.
Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.
Mark the package as acceptable risk. To ignore this alert only
in this pull request, reply with the comment
@SocketSecurity ignore npm/buffer@4.9.2. You can
also ignore all packages with @SocketSecurity ignore-all.
To ignore an alert for all future pull requests, use Socket's Dashboard to
change the triage state of this alert.
This file contains hidden or 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
dependenciesPull requests that update a dependency file
0 participants
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.
renovate
Bot
force-pushed
the
renovate/date-fns-4.x
branch
from
This PR contains the following updates:
^2.28.0→^4.4.0Release Notes
date-fns/date-fns (date-fns)
v4.4.0Compare Source
This release revisits the approach to CDN usage and introduces a new package,
@date-fns/cdnand deprecates thedate-fnsCDN scripts. It allowed reducing the zipped package size from5.83 MBdown to3.96 MBwithout introducing any breaking changes.In
v5.0.0-alpha.0where CDN scripts are completely removed fromdate-fnsthe change is more significant and brings the zipped package size down to2.89 MB.It is just the first step in optimizing the package size. Expect further size reduction in the future v4 and v5 versions.
Changed
DEPRECATED: The
date-fnsCDN scripts are now deprecated and will be removed in the next major release. Please switch to the new@date-fns/cdnpackage for CDN usage.Removed CDN source maps to reduce the package size. If you rely on them, please switch to the new
@date-fns/cdnpackage that still includes them.v4.3.0Compare Source
Kudos to @ImRodry and @puneetdixit200 for their contributions.
Fixed
Fixed missing modularized optimization fallback (for Next.js and others). See #4193.
Fixed
ptlocale first day of week to be Sunday. See #4195 by @ImRodry.Fixed
zh-CN,zh-HK, andzh-TWlocale month parsing for October, November, and December. See #4194 by @puneetdixit200.v4.2.1Compare Source
Fixed
v4.2.0Compare Source
This is a minor release in all senses, it only includes documentation updates (first of many) that points to the new You Don't Need date-fns* page.
* Not really
Changed
add,addBusinessDays, andaddDays.v4.1.0Compare Source
This release adds time zone support to format functions (that I somehow missed when working on the feature) and fixes a few bugs.
Make sure also upgrade
TZDateto v1.0.2 as it includes a bunch of critical bug fixes.Fixed
constructFromthrowing an exception onnullarguments. Whilenullisn't allowed, the functions should rather returnInvalid DateorNaNin such cases. See #3885.Added
format,formatISO,formatISO9075,formatRelativeandformatRFC3339. See #3886.v4.0.0Compare Source
I have great news! First, ten years after its release, date-fns finally gets first-class time zone support.
Another great news is that there aren't many breaking changes in this release. All of them are type-related and will affect only those explicitly using internal date-fns types. Finally, it has been less than a year since the last major release, which is an improvement over the previous four years between v2 and v3. I plan on keeping the pace and minimizing breaking changes moving forward.
Read more about the release in the announcement blog post.
- Sasha @kossnocorp
Added
Added time zones support via
@date-fns/tz'sTZDateclass andtzhelper function. See its README for the details about the API.All relevant functions now accept the context
inoption, which allows to specify the time zone to make the calculations in. If the function also returns a date, it will be in the specified time zone:In the example,
addDayswill get the current date and time in Singapore and add 5 days to it.startOfDaywill inherit the date type and return the start of the day in Singapore.Changed
The function arguments, as well as
Interval'sstartandend, now can be of different types, allowing you to mixUTCDate,TZDate,Date, and other extensions, as well as primitives (strings and numbers).The functions will normalize these values, make calculations, and return the result in the same type, preventing any bugs caused by the discrepancy. If passed, the type will be inferred from the context
inoption or the first encountered argument object type. TheInterval'sstartandendwill be considered separately, starting fromstart.In the given example, the result will be in the
TZDateas the first argument is a number, and thestarttakes precedence over theend.BREAKING: This release contains a bunch of types changes that should not affect the library's expected usage. The changes are primarily internal and nuanced, so rather than listing them here, I recommend you running the type checker after the upgrade. If there are unfixable problems, please open an issue.
BREAKING: The package now is ESM-first. The CommonJS is still support and It should not affect most users, but it might break in certains environments. If you encounter any issues, please report them.
Fixed
$by properly wrapping the code in an IIFE.v3.6.0Compare Source
On this release worked @kossnocorp and @world1dan. Also, thanks to @seated for sponsoring me.
Fixed
formatDistance.Added
v3.5.0Compare 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
daysToWeeksreturning negative 0.Fixed German grammar for the "half a minute" string.
Added
Added the Northern Sámi (
se) locale.Added the
constructNowfunction that creates the current date using the passed reference date's constructor.v3.4.0Compare Source
Kudos to @kossnocorp, @sakamossan and @Revan99 for working on the release. Also, thanks to @seated for sponsoring me.
Added
Added
roundToNearestHoursfunction.Added Central Kurdish (
ckb) locale.v3.3.1Compare 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
truncinstead ofround. The bug was introduced in v3.3.0. The affected functions:differenceInCalendarDays,differenceInCalendarISOWeeks,differenceInCalendarWeeks,getISOWeek,getWeek, andgetISOWeeksInYear.v3.3.0Compare Source
On this release worked @kossnocorp, @TheKvikk, @fturmel and @ckcherry23.
Fixed
Fixed the bug in
getOverlappingDaysInIntervalscaused 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,quartersToMonthsandmonthsToQuarters.Fixed the Czech locale's
formatDistanceto include1informatDistance.Fixed
differenceInSecondsand 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
yearsToDaysto the FP submodule.Made functions using rounding methods always return
0instead of-0.Added
formataliasformatDatewith correspondingFormatDateOptionsinterface.v3.2.0Compare Source
This release is brought to you by @kossnocorp, @fturmel, @grossbart, @MelvinVermeer, and @jcarstairs-scottlogic.
Fixed
Fixed types compatibility with Lodash's
flowand fp-ts'spipe. (#3641)Fixed inconsistent behavior of
roundToNearestMinutes.Added
format,lightFormat, andparseinternals that enable 3rd-parties to consume those.v3.1.0Compare Source
This release is brought to you by @kossnocorp, @makstyle119 and @dmgawel.
Fixed
Added
Added
yearsToDaysfunction.Added warning about using protected tokens like
YorDwithout passing a corresponding option. See #2950.v3.0.6Compare Source
On this release worked @imwh0im, @jamcry and @tyrw.
Fixed
areIntervalsOverlappingcaused by incorrect sorting (#3614)v3.0.5Compare Source
This release is brought to you by @goku4199.
Fixed
toDatenot processing string arguments properlyv3.0.4Compare Source
This release is brought to you by @kossnocorp.
Fixed
v3.0.3Compare Source
Fixed
d.tsfiles. Instead now it copies the content to avoid the Masquerading as CJS problem reported by "Are the types wrong?".v3.0.2Compare Source
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.1Compare Source
Fixed
d.mtsfiles exporting only types.v3.0.0Compare 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.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.v2.30.0Compare Source
Kudos to @kossnocorp and @Andarist for working on the release.
Changes
v2.29.3Compare Source
This release is prepared by our own @leshakoss.
Fixed
Fixed Ukrainian (
uk) locale grammar forformatDistance.Improved browser compatibility by transforming the code with
@babel/preset-env.v2.29.2Compare Source
This release is brought to you by @nopears, @vadimpopa and @leshakoss.
Fixed
Fixed
svlocale abbreviated months matcher.Fixed
uklocale abbreviated months matcher.Fixed a breaking change in
intervalToDurationby removing a recently introduced RangeError.v2.29.1Compare Source
Thanks to @fturmel for working on the release.
Fixed
v2.29.0Compare Source
On this release worked @tan75, @kossnocorp, @nopears, @Balastrong, @cpapazoglou, @dovca, @aliasgar55, @tomchentw, @JuanM04, @alexandresaura, @fturmel, @aezell, @andersravn, @TiagoPortfolio, @SukkaW, @Zebreus, @aviskarkc10, @maic66, @a-korzun, @Mejans, @davidspiess, @alexgul1, @matroskin062, @undecaf, @mprovenc, @jooola and @leshakoss.
Added
Added
intlFormatDistancefunction`.Added
setDefaultOptionsandgetDefaultOptionsfunctions that allow you to set default default locale,weekStartsOnandfirstWeekContainsDate.Added
roundingMethodoption toroundToNearestMinutes.Added Swiss Italian locale (
it-CH).Added Occitan (
oc) locale. (#2061)Added Belarusian Classic (
be-tarask) locale.Fixed
Fixed Azerbaijani (
az) locale forformatDistance.Fixed Czech (
cs) locale forparse.Fixed TypeScript types for constants.
Fixed long formatters in the South African English locale (
en-ZA).Fixed a typo in the Icelandic locale (
is) forformat.Fixed weekday format for
formatRelativein the Portuguese locale (pt).Fixed
intervalToDurationbeing off by 1 day sometimes.Fixed ordinal number formatting in Italian locale (
it).Fixed issue parsing months in Croatian (
hr), Georgian (ka) and Serbian (srandsr-Latn) locales.Changed
Replaced
git.iolinks with full URLs in error messages.Internal: removed "v2.0.0 breaking changes" section from individual function docs
Configuration
📅 Schedule: (UTC)
🚦 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.