chore(deps): update dependency propagating-hammerjs to v3

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
propagating-hammerjs	2.0.1 -> 3.0.0

---

Release Notes

josdejong/propagating-hammerjs (propagating-hammerjs)

v3.0.0

Compare Source

• Breaking: Dropped support for IE 11
• Fix: Use event.target in cases where the target has been removed
  from the DOM (#​17). Thanks @​sgparrish.

---

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 is behind base branch, 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.

[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 could not resolve
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/propagating-hammerjs
npm ERR!   dev propagating-hammerjs@"3.0.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer propagating-hammerjs@"^1.4.0 || ^2.0.0" from [email protected]
npm ERR! node_modules/vis-timeline
npm ERR!   dev vis-timeline@"7.7.3" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/propagating-hammerjs
npm ERR!   peer propagating-hammerjs@"^1.4.0 || ^2.0.0" from [email protected]
npm ERR!   node_modules/vis-timeline
npm ERR!     dev vis-timeline@"7.7.3" 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-11T22_22_11_590Z-eresolve-report.txt

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

[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 error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: [email protected]
npm error Found: [email protected]
npm error node_modules/propagating-hammerjs
npm error   dev propagating-hammerjs@"3.0.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer propagating-hammerjs@"^1.4.0 || ^2.0.0" from [email protected]
npm error node_modules/vis-timeline
npm error   dev vis-timeline@"7.7.3" from the root project
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/propagating-hammerjs
npm error   peer propagating-hammerjs@"^1.4.0 || ^2.0.0" from [email protected]
npm error   node_modules/vis-timeline
npm error     dev vis-timeline@"7.7.3" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2024-10-30T00_02_43_149Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-10-30T00_02_43_149Z-debug-0.log