Update dependency jasmine-spec-reporter to v7

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
jasmine-spec-reporter	^2.4.0 -> ^7.0.0

---

Release Notes

bcaudan/jasmine-spec-reporter

v7.0.0

Compare Source

Bugfix

• 'SpecReporter' is not assignable to type 'Reporter | CustomReporter' #​588

Breaking change

Update signature of CustomReporterResult to fix collision with new jasmine properties

Before:

export interface CustomReporterResult extends jasmine.CustomReporterResult {
  duration?: string
}

Now:

export interface CustomReporterResult extends jasmine.CustomReporterResult {
  _jsr?: {
    formattedDuration?: string
  }
}

v6.0.0

Compare Source

Feature

• Use colors/safe #​538

Breaking change

String prototype does not contain color properties anymore, colors must now be applied with the new theme component available as a field in custom display processors.

Before:

class MyProcessor extends DisplayProcessor {
  public displaySuccessfulSpec(spec: CustomReporterResult, log: string): string {
    return 'OK '.successful + log
  }
}

Now:

class MyProcessor extends DisplayProcessor {
  public displaySuccessfulSpec(spec: CustomReporterResult, log: string): string {
    return this.theme.successful('OK ') + log
  }
}

v5.0.2

Compare Source

Bugfix

• pretty stacktrace: catch uncaught exception on node internal files #​479

v5.0.1

Compare Source

Bugfix

• Promote colors as a dependency #​472

v5.0.0

Compare Source

Feature

• New option to display pretty stacktraces #​467

Breaking change

displayStacktrace options now take a value among none, raw and pretty.

v4.2.1

Compare Source

Bugfix

• Restore compatibility with jasmine < 2.5.0 #​222, #​223

v4.2.0

Compare Source

Feature

• Support reporting errors in afterAll #​210, #​214

v4.1.1

Compare Source

Bugfix

• Correct report from jasmineStarted event #​185

v4.1.0

Compare Source

Feature

• If any defined spec is not executed, report INCOMPLETE rather than SUCCESS #​142, #​145

Other

• Rewrite unit tests by bumping jasmine-core to 2.6.x #​155
• Use yarn for development #​98, #​138
• Add greenkeeper-yarn.sh to automatically updates yarn.lock on greenkeeper PR

v4.0.0

Compare Source

• Use string primitive instead of String wrapper object #​134, #​137

Breaking change

It only impacts TypeScript integrations, DisplayProcessor methods signature now use string instead of String.

Before:

displaySuite(suite: CustomReporterResult, log: String): String;

Now:

displaySuite(suite: CustomReporterResult, log: string): string;

v3.3.0

Compare Source

• Add low-level print configuration option #​129, #​130

v3.2.0

Compare Source

• Add an option to remove duration from execution summary.
• Add jasmine & protractor integration tests #​82

v3.1.0

Compare Source

• Add displaySpecErrorMessages and displaySummaryErrorMessages to DisplayProcessor #​85
• Add an option to remove error messages #​62
• Add an option to customize stacktrace filtering #​72

v3.0.0

Compare Source

Breaking changes

• Remove support for node 0.10

• jasmine-spec-reporter module exports SpecReporter and DisplayProcessor, see SpecReporter and DisplayProcessor usages.

• Extract groups in configuration and rationalize property names, see new structure. #​57

• Colors deactivation is now achieved with this configuration:

  {
    colors: {
      enabled: false
    }
  }
  

• Custom options for custom processors must now be stored in this configuration field:

  {
    customOptions: {
      foo: 'bar'
    }
  }
  

Other

• Migrate code base to TypeScript
• Add example for TypeScript integration
• Extract each example in a dedicated node module, see examples

---

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 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]

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.