Open greenkeeper[bot] opened 5 years ago
coveralls
commented
5 years ago Coverage remained the same at 95.349% when pulling ddbff64f35f8071e9d216c5e5b3e0e95176d690c on greenkeeper/karma-coverage-2.0.0 into 6957ec52a1e1b114d771014b282e3934f258bd1c on master.
greenkeeper[bot]
commented
5 years ago devDependency karma-coverage was updated from 1.1.2 to 2.0.1.greenkeeper[bot]
commented
4 years ago devDependency karma-coverage was updated from 1.1.2 to 2.0.2.
The devDependency karma-coverage was updated from
1.1.2to2.0.0.This version 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.
Publisher: karmarunnerbot License: MIT
Release Notes for v2.0.0
Bug Fixes
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.
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.
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:
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.
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.
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.
This commit updates the report creator utility to allow resetting the
custom reporter map.
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.
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.
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.
:Commits
The new version differs by 14 commits.
0e2800bchore: release v2.0.099c0c35chore: update contributorsf40d6afchore(deps): Use latest istanbul lib packages (#377)b8f82a0Update grunt dependencies (#374)b51cee7Update test dependencies (#373)14c8cbaMerge pull request #372 from hicom150/update_eslint_dependenciesa6b0f17Merge branch 'master' into update_eslint_dependenciesac445f1Merge pull request #371 from hicom150/update_travis00090eachore: Update travis configeefaaa2style(eslint): Fix ESLint errorsd40463dchore: Update ESLint dependenciesc642c6bUpdate travis to match parent karma projecte288ca4Update travis to match parent karma project15f8b12fix: bump lodash for CVE-2018-16487See the full diff
FAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper bot :palm_tree: