Skip to content

mikhail-ev/coverage-inspector

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

8 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

coverage-inspector

GUI Inspector for Google Chrome's coverage report. Uses sourcemaps to link bundle's lines to their source in the project. Based on mozilla/source-map.

Features:

  • Re-creates project's used file structure for a specific page.
  • Gives side-by-side view of a file in the bundle and highlights its boundaries.
  • Shows duplicates in the final bundle.
  • Shows unused lines in the original, not-minified file

Quickstart

1. Install CLI

npm i -g coverage-inspector

2. Get a coverage report

Create a coverage report using Chrome's Coverage tab. Please follow its documentation. And export the JSON afterwards:

highlight of the coverage's export button

3. Parse the report

    coverage-inspector parse -i <path-to-your-report> [-n <name-to-override-default-output-filename>]

Check out an example of an output generated for this page.

Commands

Parse

coverage-inspector parse

Parse a coverage file and generate a report

Options:
      --version                        Show version number             [boolean]
      --help                           Show help                       [boolean]
  -i, --input                          Path to a Chrome coverage report
                                                             [string] [required]
  -v, --verbosity                      Set level of verbosity
         [string] [choices: "debug", "warnings", "errors"] [default: "warnings"]
  -n, --filename                       Filename to replace automatically
                                       generated
                                       "coverage-report_${timestamp}.html"
                                                                        [string]
  -o, --output-dir                     Set output directory
                                                         [string] [default: "."]
      --search-start-in-lines, --ssil  In how many lines to search for the start
                                       if the sourcemap doesn't start with the
                                       first line of the source
                                                         [number] [default: 200]

Contribution

TBD

Roadmap

TBD

About

GUI Inspector for Google Chrome's coverage report

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

 
 
 

Contributors