Update dependency karma-chrome-launcher to ~3.2.0 - autoclosed

[renovate[bot]]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
karma-chrome-launcher	~3.1.0 -> ~3.2.0

---

Release Notes

karma-runner/karma-chrome-launcher (karma-chrome-launcher)

### [`v3.2.0`](https://togithub.com/karma-runner/karma-chrome-launcher/blob/HEAD/CHANGELOG.md#320-2023-04-20) [Compare Source](https://togithub.com/karma-runner/karma-chrome-launcher/compare/v3.1.1...v3.2.0) ##### Features - add process.env.ProgramW6432 as root location for binaries ([12a73db](https://togithub.com/karma-runner/karma-chrome-launcher/commit/12a73dba261c78fdba4aff4dbb741ac87adfed01)) #### [3.1.1](https://togithub.com/karma-runner/karma-chrome-launcher/compare/v3.1.0...v3.1.1) (2022-03-09) ##### Bug Fixes - artificially trigger a release ([83fdc3c](https://togithub.com/karma-runner/karma-chrome-launcher/commit/83fdc3ca5666374c677408ed0589e66b1124bec4)) ### [`v3.1.1`](https://togithub.com/karma-runner/karma-chrome-launcher/blob/HEAD/CHANGELOG.md#311-2022-03-09) [Compare Source](https://togithub.com/karma-runner/karma-chrome-launcher/compare/v3.1.0...v3.1.1) ##### Bug Fixes - artificially trigger a release ([83fdc3c](https://togithub.com/karma-runner/karma-chrome-launcher/commit/83fdc3ca5666374c677408ed0589e66b1124bec4))

---

Configuration

📅 Schedule: Branch creation - "after 8am and before 5pm on saturday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ 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 has been generated by Mend Renovate. View repository job log here.

[renovate[bot]]

⚠ 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: @angular/cdk@14.2.4
npm ERR! Found: @angular/common@16.2.12
npm ERR! node_modules/@angular/common
npm ERR!   @angular/common@"16.2.12" from the root project
npm ERR!   peer @angular/common@"16.2.12" from @angular/forms@16.2.12
npm ERR!   node_modules/@angular/forms
npm ERR!     @angular/forms@"16.2.12" from the root project
npm ERR!   5 more (@angular/platform-browser, ...)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer @angular/common@"^14.0.0 || ^15.0.0" from @angular/cdk@14.2.4
npm ERR! node_modules/@angular/cdk
npm ERR!   peer @angular/cdk@">=14.0.0" from ng2-charts@4.1.1
npm ERR!   node_modules/ng2-charts
npm ERR!     ng2-charts@"4.1.1" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: @angular/common@15.2.10
npm ERR! node_modules/@angular/common
npm ERR!   peer @angular/common@"^14.0.0 || ^15.0.0" from @angular/cdk@14.2.4
npm ERR!   node_modules/@angular/cdk
npm ERR!     peer @angular/cdk@">=14.0.0" from ng2-charts@4.1.1
npm ERR!     node_modules/ng2-charts
npm ERR!       ng2-charts@"4.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! 
npm ERR! For a full report see:
npm ERR! /tmp/worker/9b2b35/73f325/cache/others/npm/_logs/2023-11-09T12_25_34_926Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/worker/9b2b35/73f325/cache/others/npm/_logs/2023-11-09T12_25_34_926Z-debug-0.log