@cypress/code-coverage - npm Package Compare versions

Comparing version 3.10.0 to 3.10.1

package.json

 {
   "name": "@cypress/code-coverage",
-  "version": "3.10.0",
+  "version": "3.10.1",
   "description": "Saves the code coverage collected during Cypress tests",
@@ -56,3 +56,3 @@ "main": "index.js",
     "istanbul-lib-coverage": "3.0.0",
-    "js-yaml": "3.14.1",
+    "js-yaml": "4.1.0",
     "nyc": "15.1.0"
@@ -69,3 +69,3 @@ },
     "lodash": "4.17.21",
-    "markdown-link-check": "3.9.0",
+    "markdown-link-check": "3.11.0",
     "parcel-bundler": "1.12.5",
@@ -72,0 +72,0 @@ "prettier": "2.6.2",

README.md

@@ -43,3 +43,3 @@ # @cypress/code-coverage [![renovate-app badge][renovate-badge]][renovate-app] [![CircleCI](https://circleci.com/gh/cypress-io/code-coverage.svg?style=svg)](https://circleci.com/gh/cypress-io/code-coverage)
 
-Please see the [Test Apps](#test-apps) section down below, you can probably find a linked project matching your situation to see how to instrument your application's source code before running end-to-end tests to get the code coverage.
+Please see the [Test Apps](#internal-test-apps) section down below, you can probably find a linked project matching your situation to see how to instrument your application's source code before running end-to-end tests to get the code coverage.
 
@@ -377,3 +377,3 @@ If your application has been instrumented correctly, then you should see additional counters and instructions in the application's JavaScript resources, like the image down below shows.
 # or pass the environment variable
-CYPRESS_coverage=false cypress run
+CYPRESS_COVERAGE=false cypress run
 ```
@@ -418,3 +418,3 @@
 - [test-apps/before-each-visit](test-apps/new-cypress-config/before-each-visit) checks if code coverage correctly keeps track of code when doing `cy.visit` before each test
-- [test-apps/one-spec.js](test-apps/new-cypress-config/one-spec.js) confirms that coverage is collected and filtered correctly if the user only executes a single Cypress test
+- [test-apps/one-spec](test-apps/new-cypress-config/one-spec) confirms that coverage is collected and filtered correctly if the user only executes a single Cypress test
 - [test-apps/ts-example](test-apps/new-cypress-config/ts-example) uses Babel + Parcel to instrument and serve TypeScript file
@@ -421,0 +421,0 @@ - [test-apps/use-webpack](test-apps/new-cypress-config/use-webpack) shows Webpack build with source maps and Babel

support.js

@@ -217,3 +217,3 @@ /// <reference types="cypress" />
 // or
-//  CYPRESS_coverage=false cypress run
+//  CYPRESS_COVERAGE=false cypress run
 // see https://on.cypress.io/environment-variables
@@ -220,0 +220,0 @@

New alerts

License Policy Violation

License

This package is not allowed per your license policy. Review the package's license to ensure compliance.

Found 1 instance in 1 package

Fixed alerts

License Policy Violation

License

This package is not allowed per your license policy. Review the package's license to ensure compliance.

Found 1 instance in 1 package

Improved metrics

Total package byte prevSize

63445

Dependency changes

• + Addedargparse@2.0.1(transitive)

• + Addedjs-yaml@4.1.0(transitive)

• Updatedjs-yaml@4.1.0