[Snyk] Upgrade chrono-node from 2.8.0 to 2.9.0

[hkambham]

Snyk has created this PR to upgrade chrono-node from 2.8.0 to 2.9.0.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

---

• The recommended version is 6 versions ahead of your current version.

• The recommended version was released 21 days ago.

Release notes

Package name: chrono-node

• 2.9.0 - 2025-09-23
  

  New/Fix: Remove dayjs dependency

  We have been working toward making Chrono relying only on native Javascript date/time library; and now we are ready to drop dayjs dependency.

  This change removes ParsingComponent.dayjs() and dayjs from package.json (50585af). Thus, it is published in a minor version.

  ---

  v2.8.5...v2.9.0

• 2.8.5 - 2025-09-23
  
  • New: export it and sv locales f13e64e
  • Fix: Do not parse year-like numbers as times deb72c5
  • Fix: JP time parsing improvement b1bde28

  ---

  v2.8.4...v2.8.5

• 2.8.4 - 2025-08-04
  
  • Fix: Timezone override in the options is not correctly applied in reference #608, 958eb3d
  • New: Swedish (SW) initial support (by @ Nicklasfox) a5c52cf.

  ---

  v2.8.3...v2.8.4

• 2.8.3 - 2025-06-14
  
  • Rewrite duration calculations (without DayJs) abba434
  • Fix: (en) "noon" time assignment confidence (by @ crazyjncsu)
  • Fix: export type ParsingContext (by @ wickedest)

  ---

  v2.8.2...v2.8.3

• 2.8.2 - 2025-06-01
  
  • Fix: Correct import error in 2.8.1

  ---

  v2.8.1...v2.8.2

• 2.8.1 - 2025-05-25
  
  • Fix: ignore short digits following date (#595 ) 971b833
  • Refactor: Update the devDependencies 174b35e
  • [JP] Various NL improvement by @ koji520 (#594 )

  ---

  v2.8.0...v2.8.1

• 2.8.0 - 2025-04-06
  

  New/Fix: Reference date calculation on the assigned timezone 4033a27

  Previously, the reference date calculation (e.g., "1 day ago", "tomorrow at 9am") was based on the interpretation of the reference instant/timestamp using the system timezone rather than the assigned timezone (e.g., "April 5" in the system timezone may already "April 6" in the assigned timezone).

  const refInstant = new Date("2025-02-27T22:00:00.000Z");
  // This instant/timestamp
  // = Thu Feb 27 2025 15:00:00 GMT-0800 (PST)
  // = Fri Feb 28 2025 08:00:00 GMT+0900 (JST)

  chrono.parseDate("Tomorrow at 9am", { instant: refInstant, timezone: "PST" })
  // In PST, "Tomorrow at 9am" => Fri Feb 28 2025 09:00:00 GMT-0800 (PST)

  chrono.parseDate("Tomorrow at 9am", { instant: refInstant, timezone: "JST" })
  // In JST, "Tomorrow at 9am" => Sat Mar 1 2025 09:00:00 GMT+0900 (JST)

  This changed some current relative date/time output. So, it is published in a minor version, instead of a patch.

  ---

  v2.7.9...v2.8.0

from chrono-node GitHub release notes

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• This PR was automatically created by Snyk using the credentials of a real user.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

• 🧐 View latest project report
• 📜 Customise PR templates
• 🛠 Adjust upgrade PR settings
• 🔕 Ignore this dependency or unsubscribe from future upgrade PRs