fix(deps): update dependency i18next-browser-languagedetector to v8

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
i18next-browser-languagedetector	^7.0.1 -> ^8.0.0

---

Release Notes

i18next/i18next-browser-languageDetector (i18next-browser-languagedetector)

v8.2.0

Compare Source

• feat: add support for hash detector 304

v8.1.0

Compare Source

• feat: add support for Partitioned cookies 303

v8.0.5

Compare Source

• check for common xss attack patterns on detected language

v8.0.4

Compare Source

• fix localstorage check to try to address 297 300

v8.0.3

Compare Source

• change localstorage check to try to address 297

v8.0.2

Compare Source

• fix for when passed services are null, should address 296

v8.0.1

Compare Source

• some environments, throws when accessing document.cookie

v8.0.0

Compare Source

• chore: set browsers target to defaults 286
• perf: use object deconstruction, optional chaining and hot path optimisations 287

v7.2.2

Compare Source

v7.2.1

Compare Source

• fix: align addDetector impementation to type definition 282

v7.2.0

Compare Source

• fix: separate cjs and mjs typings

v7.1.0

Compare Source

• introduce convertDetectedLanguage option

v7.0.2

Compare Source

• simplify usage without i18next

---

Configuration

📅 Schedule: Branch creation - "every 2 weeks on Monday before 7am" in timezone Europe/Berlin, 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 could not resolve
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/react
npm ERR!   react@"^18.2.0" from the root project
npm ERR!   peer react@">=16.3" from @fortawesome/[email protected]
npm ERR!   node_modules/@fortawesome/react-fontawesome
npm ERR!     @fortawesome/react-fontawesome@"^0.2.0" from the root project
npm ERR!   8 more (@react-leaflet/core, react-dom, react-i18next, ...)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer react@"^15.0.0 || ^16.0.0 || ^17.0.0" from [email protected]
npm ERR! node_modules/react-leaflet-textpath
npm ERR!   react-leaflet-textpath@"^2.1.1" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/react
npm ERR!   peer react@"^15.0.0 || ^16.0.0 || ^17.0.0" from [email protected]
npm ERR!   node_modules/react-leaflet-textpath
npm ERR!     react-leaflet-textpath@"^2.1.1" 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 /runner/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /runner/cache/others/npm/_logs/2025-11-18T23_14_48_492Z-debug-0.log

[netlify]

❌ Deploy Preview for tsb-tech-map failed.

Name	Link
🔨 Latest commit	2353ed4
🔍 Latest deploy log	https://app.netlify.com/sites/tsb-tech-map/deploys/66a6c7265d4af10008ecc7ed