fix(deps): update dependency react-leaflet to v4 - abandoned

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
react-leaflet (source)	^3.2.5 -> ^4.0.0

---

Release Notes

PaulLeCam/react-leaflet (react-leaflet)

v4.2.1

Compare Source

Fixed bounds update in ImageOverlay
(PR #​1063 by
hwonyo)

v4.2.0

Compare Source

Added support for mutable url prop on TileLayer
(PR #​1047 by
goto-bus-stop)

v4.1.0

Compare Source

• Updated Leaflet dependency to v1.9.
• Fixed eventHandlers object being injected in WMS request URL.
• Added support for dynamic bounds props on ImageOverlay.

v4.0.2

Compare Source

• Fix typos in getting started docs
  (PR #​1013 by
  jacobtylerwalls)
• Fixing useRef() usage in createElementHook to prevent unnecessary Leaflet
  object creation
  (PR #​1014 by
  abac)

v4.0.1

Compare Source

Fix calling map.remove() on MapContainer unmounting.

v4.0.0

Compare Source

Changes from v3:

Breaking changes

• React v18 and Leaflet v1.8 are now required as peer dependency.
• ES2020 is the new compilation target version.
• Removed useMapElement hook.
• Removed MapConsumer component.
• Removed whenCreated property from the MapContainer component (a ref
  callback can be used instead).
• Removed onOpen and onClose properties from Popup and Tooltip
  components.
• Removed CommonJS distribution.
• Removed UMD distribution.

Other changes

• Added support for React v18 (concurrent mode).
• Added support for ref in the MapContainer and Pane components.
• Added createLeafletContext function to core.
• The created element and context objects are now frozen (immutable).

---

Configuration

📅 Schedule: Branch creation - "before 4am on the first day of the month" (UTC), 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.

[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: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/react
npm ERR!   react@"^17.0.1" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer react@"^18.0.0" from [email protected]
npm ERR! node_modules/react-leaflet
npm ERR!   react-leaflet@"^4.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! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

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

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

[renovate]

Autoclosing Skipped

This PR has been flagged for autoclosing. However, it is being skipped due to the branch being already modified. Please close/delete it manually or report a bug if you think this is in error.