fix: output good message to the console if coverage not found

Author: bahmutov

Diff for: README.md

@@ -53,6 +53,11 @@ If you have instrumented your application's code and see the `window.__coverage_
 
 That should be it!
 
+### More information
+
+- Read [Cypress Code Coverage: Instrumenting code](https://on.cypress.io/code-coverage#Instrumenting-code) guide
+- Watch [Code coverage](https://youtu.be/C8g5X4vCZJA) webinar
+
 ### App vs unit tests
 
 You need to instrument your web application. This means that when the test does `cy.visit('localhost:3000')` any code the `index.html` requests should be instrumented by YOU. See [Examples](#examples) section for advice, usually you need to stick `babel-plugin-istanbul` into your pipeline somewhere.

Diff for: examples/use-webpack/README.md

@@ -3,3 +3,5 @@
 > Instruments the built bundle using Webpack
 
 Webpack uses [webpack.config.js](webpack.config.js) to build the bundle from [src/index.js](src/index.js) into `dist/main.js`, loaded from [dist/index.html](dist/index.html). The [cypress/integration/spec.js](cypress/integration/spec.js) also uses one of the functions from [src/calc.js](src/calc.js) directly. The final coverage includes both E2E and unit test coverage information.
+
+**Note:** this project requires `npm run build` before running `npm run dev`.

Diff for: examples/use-webpack/dist/index.html

@@ -4,11 +4,9 @@
     <title>Webpack example</title>
     <style>
       .console-log-div {
-        width: 95% !important;
         background-color: #efefef;
       }
       #log {
-        margin: 10px 0px;
         display: block;
         white-space: pre;
         font-family: monospace;