search

bkeepers / parse-reminder

a node module to parse natural language reminders into who, what, and when
ISC License
22 stars 7 forks source link

Bump chrono-node from 1.3.5 to 2.2.4 #12

Closed dependabot[bot] closed 2 years ago

dependabot[bot] commented 3 years ago

Bumps chrono-node from 1.3.5 to 2.2.4.

Release notes

Sourced from chrono-node's releases.

v2.2.4

  • Fix: improve parsing performance by caching complied regex 036f7aa
  • Fix: unblounded regex backtracking in timeunit parsing 98815b5

https://github.com/wanasit/chrono/compare/v2.2.3...v2.2.4

v2.2.3

  • Fix: vague time parsing in strict mode b582ae7
  • Add Typedoc integration 3d044ee
  • Fix: Import bug in v2.2.2 16737f5

https://github.com/wanasit/chrono/compare/v2.2.1...v2.2.3

v2.2.1

  • Fix: time expression ending with numbers only
  • New: Make (in|within|for) optional if forwardDate=true (#372)
  • New: Improved NL support (#373)

https://github.com/wanasit/chrono/compare/v2.2.0...v2.2.1

v2.2.0

  • (minor-incompatible) Removing edge-case time checking for ambitious case-like "midnight" or "tomorrow" at ~1AM.
  • Fix: stop guessing single digit after dot as minute (#374)

https://github.com/wanasit/chrono/compare/v2.1.11...v2.2.0

v2.1.11

  • Fix: when parsing relative time, also imply time milisecond unit
  • Bump dayjs and typescript version

https://github.com/wanasit/chrono/compare/v2.1.10...v2.1.11

v2.1.10

  • [New/Fix] Improve certainty-level and timezone handling in relative time parsing (#175)
  • [Fix] short month names handling (#357)
  • [Fix] "for" time unit reference

https://github.com/wanasit/chrono/compare/v2.1.9...v2.1.10

v2.1.9

  • [Fix] handle some preprosition words in within format parser 8dfc495
  • [Fix] timezone offset hour only handling a186fdf
  • [Fix] pattern year-month-day handling 76d493b
  • [New] Add NL locale

https://github.com/wanasit/chrono/compare/v2.1.8...v2.1.9

v2.1.8

  • [New] Added FR timeunit date/time parsing
  • [New] Add Portuguese (PT) language support

... (truncated)

Commits


Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/bkeepers/parse-reminder/network/alerts).
dependabot[bot] commented 2 years ago

Looks like chrono-node is up-to-date now, so this is no longer needed.