Skip to content

Update dependency karma-coverage to v2

renovate-bot requested to merge renovate/karma-coverage-2.x into develop

This MR contains the following updates:

Package Type Update Change
karma-coverage devDependencies major 1.1.2 -> 2.2.0

Release Notes

karma-runner/karma-coverage

v2.2.0

Compare Source

Features
  • update Istanbul packages (24aac11)

2.1.1 (2022-02-05)

Bug Fixes

v2.1.1

Compare Source

Bug Fixes

v2.1.0

Compare Source

Bug Fixes
  • deps: update main and dev dependencies (c20d982)
Features
  • reporter: log coverage threshold as a warning fixed #​432 (a6c95d8)

2.0.3 (2020-07-24)

Bug Fixes
  • report: waiting promise resolve in onExist method fix #​418 (c93f061)

2.0.2 (2020-04-13)

Bug Fixes

2.0.1 (2019-08-20)

v2.0.3

Compare Source

Bug Fixes
  • report: waiting promise resolve in onExist method fix #​418 (c93f061)

v2.0.2

Compare Source

Bug Fixes

v2.0.1

Compare Source

2.0.1 (2019-08-20)

v2.0.0

Compare Source

Bug Fixes
  • build: Update to lodash 4 (d6d21d2), closes #​242
  • reporter: replace colons in the output path (3b2bffa)
  • bump lodash for CVE-2018-16487 (15f8b12)
Chores
BREAKING CHANGES

  • deps: This set of changes may impact some use cases.

  • chore: Add Updated Istanbul Dependencies

The istanbul package is deprecated in favor several split packages that control different aspects of how istanbul works. This commit adds the recommended packages that will be used in future commits as karma-coverage's usage of istanbul is updated to the latest api.

  • refactor(reporter): Follow new report API

This commit refactors the in memory report implementation to use the new istanbul report API.

Report creation is removed from newer versions of the istanbul API, so this commit adds a set of utility functions to wrap around the new API and provide similar functionality as the old API. The top level export uses the new utility function to register the in-memory report.

  • refactor(preprocessor): Switch to istanbul-lib-instrument

This commit updates the preprocessor to use istanbul-lib-instrument instead of the deprecated istanbul package. The biggest change in this refactor is using a callable function instead of a constructor when creating instrumenters

The old istanbul package exposed the Instrumenter directly, allowing the preprocessor to create an instance of it. istanbul-lib-instrument, however, exposes a callable function that creates an Instrumenter. This commit updates the preprocessor to follow this new pattern of using a callable function. In order to ensure backwards compatibility, a utility function is added to wrap constructors with a callable function for creation automatically.

This change allows the following configuration for creating instrumenters:

  1. An object that contains an Instrumenter constructor
  2. An Instrumenter constructor itself
  3. A callable function that returns an Instrumenter instance.

This commit also uses the istanbul-lib-source-maps package to handle storing source maps. A global source map store registers source maps so they can be used later on in the reporter.

  • refactor(reporter): Switch to istanbul-lib-coverage

This commit updates the reporter by using the istanbul-lib-coverage package api for handling coverage checking/management and the istanbul-lib-report package api for handling reporting.

The new apis remove the need for collectors and remove the need to handle disposing collectors.

  • refactor: Remove unused source cache utilities

This commit removes the source-cache-store and source-cache files as they are no longer being used. The source-map-store and istanbul-lib-source-maps are used instead, so these files are no longer needed.

  • feat(util): Add Reset Functionality

This commit updates the report creator utility to allow resetting the custom reporter map.

  • fix(preprocessor): Track Coverage Maps Properly

This commit updates the preprocessor to properly access file coverage when storing it in the global coverage map (when includeAllSources is true). The previous method did not work because the returned instrumented code from the default istanbul instrumenter returns the coverage map in a POJO object instead of JSON notation. This breaks the coverage regex used to match and parse the coverage map.

The istanbul instrumenter offers the ability to receive the coverage map for the last instrumented file through a separate function, so that is tested for and used if it is supported. The original method is used as a fallback for backwards compatibility.

This commit also addresses changes from the v0 instanbul instrumenter options. The changes are additive only to maintain backwards compatibility for other instrumenters.

  • fix(reporter): Access Data Properly to Check Coverage

This commit fixes errors with accessing data properly during the checkCoverage method. A previous commit updated the implementation to use istanbul-lib-coverage, but this involved an api change to access the raw coverage data (which checkCoverage uses).

This commit also fixes the checking coverage for each file by using a map to store file coverage summaries instead of merging summaries like the global results. Per file coverage now works as expected.

  • test: Update Unit Tests to use new Istanbul API

This commit updates the mocking done in unit tests to properly mock the new istanbul API. Additionally, new unit test suites are added for the utility methods report-creator and source-map-store.

  • drop support for node < 8
  • reporter: the output folder names change, they no longer contain :

1.1.2 (2018-05-03)

Bug Fixes
  • build: Update to lodash 4 (d6d21d2), closes #​242
  • reporter: replace colons in the output path (3b2bffa)
BREAKING CHANGES
  • reporter: the output folder names change, they no longer contain :

1.1.1 (2016-07-23)

Bug Fixes
  • remove usage of the deprecated helper._ (dacf9e9)

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 MR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this MR and you won't be reminded about this update again.

  • If you want to rebase/retry this MR, click this checkbox.

This MR has been generated by Renovate Bot.

Merge request reports