chore(deps): update dependency karma-jasmine-html-reporter to v2

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
karma-jasmine-html-reporter	0.2.2 -> 2.1.0

---

Release Notes

dfederm/karma-jasmine-html-reporter (karma-jasmine-html-reporter)

v2.1.0

Compare Source

v2.0.0

Compare Source

This version rewrites the package to use the peer jasmine-core package instead of repackaging the html reporting code. This fixes support for Jasmine v4 and (hopefully) will require less package updates going forward.

v1.7.0

Compare Source

Upgrade to Jasmine 3.8

v1.6.0

Compare Source

Upgrade to Jasmine 3.7.1

v1.5.4

Compare Source

Manually integrate unreleased Jasmine fix: jasmine/jasmine@2b318a6

v1.5.3

Compare Source

Added suppressAll option to config (#​40)

v1.5.2

Compare Source

Added options object to be able to overwrite logging (#​36)

v1.5.1

Compare Source

Fix bad merge, re-do #​25

v1.5.0

Compare Source

Upgraded to Jasmine 3.5

v1.4.2

Compare Source

Only override specFilter if query exists

v1.4.1

Compare Source

Respect spec filters set by other plugins.

v1.4.0

Compare Source

• Upgraded to Jasmine 3.3

v1.3.1

Compare Source

• Updated Jasmine-core in peerDependencies to minimum version 3.2 so that npm will produce a warning when using an older version.

v1.3.0

Compare Source

Sync with Jasmine v3.2.0, which includes:

• Line-break long expectation failure messages (jasmine/jasmine@e2d9eef)
• Implemented hiding of disabled specs (jasmine/jasmine@3636014)

v1.2.0

Compare Source

• Change peer dependency on Jasmine to Jasmine Core

v1.1.0

Compare Source

• Sync with the latest Jasmine code
• Add script to sync with latest Jasmine code

v1.0.0

Compare Source

• Support Jasmine >= 3.0.0

---

Configuration

📅 Schedule: Branch creation - "before 4am on Monday" in timezone America/New_York, 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 error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: [email protected]
npm error Found: [email protected]
npm error node_modules/jasmine-core
npm error   dev jasmine-core@"2.6.4" from the root project
npm error
npm error Could not resolve dependency:
npm error peer jasmine-core@"^4.0.0 || ^5.0.0" from [email protected]
npm error node_modules/karma-jasmine-html-reporter
npm error   dev karma-jasmine-html-reporter@"2.1.0" 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-11-21T11_55_41_688Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-11-21T11_55_41_688Z-debug-0.log

[BilalQamar95]

Closing this PR as it requires upgrading jasmine-core to ^4.0.0 || ^5.0.0 to resolve the dependency conflict with [email protected]. Once jasmine-core is upgraded, we can revisit and proceed with this update.

[renovate]

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 2.x releases. But if you manually upgrade to 2.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.