Update dependency date-fns-tz to v3

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
date-fns-tz	^2.0.0 -> ^3.0.0

---

Release Notes

marnusw/date-fns-tz (date-fns-tz)

v3.2.0

Compare Source

• [DEPS] date-fns@4.0.0 supported (#​301)
• [PERFORMANCE] Make testDateFormatted static to avoid re-initialising it on every call (#​297) @​hurali97
• [ENHANCEMENT] Compatibility with date-fns setDefaultOptions (#​286) @​yangchristina
• [DOCS] Fixed table of contents links (#​284)

v3.1.3

Compare Source

• [BUGFIX] Make getTimeZoneOffset's 2nd arg optional

v3.1.2

Compare Source

• [BUGFIX] Fix formatInTimeZone use of timeZone string (#​280)

v3.1.1

Compare Source

• [BUGFIX] getTimeZoneOffset's 2nd arg should be optional (#​281)

v3.1.0

Compare Source

• [REFACTOR] Full rewrite in TypeScript (#​278) Thank you, @​brettwillis
• [BREAKING CHANGE] OptionsWithTZ is now either FormatOptionsWithTZ or ToDateOptionsWithTZ, matching date-fns

v3.0.1

Compare Source

• [BUGFIX] Fix named export typings (#​277)

v3.0.0

Compare Source

• [UPGRADE] Support date-fns v3 (#​265) Thank you, @​christopherklint97
• [BUGFIX] Correct import of date-fns@v3 format and use Babel Webpack loader for mjs files (#​271)
• [BREAKING CHANGE] date-fns v2 is no longer supported
• [BREAKING CHANGE] Renamed utcToZonedTime to toZonedTime to make the name less confusing, just search & replace
• [BREAKING CHANGE] Renamed zonedTimeToUtc to fromZonedTime to make the name less confusing, just search & replace
• [BREAKING CHANGE] All functions are now exported using named exports, this requires changing direct
  imports from import formatInTimeZone from 'date-fns-tz/formatInTimeZone' to
  import { formatInTimeZone } from 'date-fns-tz/formatInTimeZone'
• [BREAKING CHANGE] Functions now don’t check the number of passed arguments, delegating this task to type checkers
  (This isn't fully implemented yet, but it should be the assumption moving forward, as it is in date-fns)
• [BREAKING CHANGE] Arguments are not explicitly converted to the target types. Instead, they are passed as is,
  delegating this task to type checkers (This isn't fully implemented yet, but it should be the assumption
  moving forward, as it is in date-fns)
• [BREAKING CHANGE] IE is no longer supported since date-fns no longer supports it
• [BREAKING CHANGE] Removed flow support since date-fns also removed it

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
nyuusu	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Apr 6, 2024 8:24am

[renovate]

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: nyuusu@1.0.0
npm ERR! Found: date-fns@2.30.0
npm ERR! node_modules/date-fns
npm ERR!   date-fns@"^2.30.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer date-fns@"^3.0.0" from date-fns-tz@3.0.0
npm ERR! node_modules/date-fns-tz
npm ERR!   date-fns-tz@"^3.0.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! 
npm ERR! For a full report see:
npm ERR! /tmp/renovate/cache/others/npm/_logs/2024-04-06T08_24_28_056Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-04-06T08_24_28_056Z-debug-0.log