Update karma-coverage to the latest version 🚀

[greenkeeper]

Version 1.1.2 of karma-coverage was just published.

Dependency	karma-coverage
Current Version	1.1.1
Type	devDependency

The version 1.1.2 is not covered by your current version range.

If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.

It might be worth looking into these changes and trying to get this project onto the latest version of karma-coverage.

If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.

---

Release Notes

v1.1.2

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 :

Commits

The new version differs by 12 commits.

• 070bba3 chore: release v1.1.2
• 9319dfb chore: update contributors
• 9433b24 Merge pull request #339 from johnjbarton/fix-242
• bf599db Merge pull request #344 from AndrewLane/AndrewLane-patch-1
• 595ab98 Fix exclude typo on the check object
• d6d21d2 fix(build): Update to lodash 4
• 954a555 Merge pull request #345 from johnjbarton/engines
• d4695cf Update travis to match parent karma project
• 54737bf chore: add grunt-cli npm test works out of the box
• 2bc4aa5 docs: add json-summary report type
• 3b2bffa fix(reporter): replace colons in the output path
• 1a876d5 docs: Added none as possible value for type

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper bot 🌴

[coveralls]

Coverage remained the same at 100.0% when pulling 52481fa on greenkeeper/karma-coverage-1.1.2 into 8b0e62d on master.

[greenkeeper]

• The devDependency karma-coverage was updated from 1.1.1 to 2.0.0.

Update to this version instead 🚀

Release Notes for v2.0.0

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

• Update travis config (00090ea)
• deps: Use latest istanbul lib packages (#377) (f40d6af)

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 :

Commits

The new version differs by 14 commits.

• 0e2800b chore: release v2.0.0
• 99c0c35 chore: update contributors
• f40d6af chore(deps): Use latest istanbul lib packages (#377)
• b8f82a0 Update grunt dependencies (#374)
• b51cee7 Update test dependencies (#373)
• 14c8cba Merge pull request #372 from hicom150/update_eslint_dependencies
• a6b0f17 Merge branch 'master' into update_eslint_dependencies
• ac445f1 Merge pull request #371 from hicom150/update_travis
• 00090ea chore: Update travis config
• eefaaa2 style(eslint): Fix ESLint errors
• d40463d chore: Update ESLint dependencies
• c642c6b Update travis to match parent karma project
• e288ca4 Update travis to match parent karma project
• 15f8b12 fix: bump lodash for CVE-2018-16487

See the full diff

[greenkeeper]

• The devDependency karma-coverage was updated from 1.1.1 to 2.0.1.

Update to this version instead 🚀

[greenkeeper]

• The devDependency karma-coverage was updated from 1.1.1 to 2.0.2.

Update to this version instead 🚀