PhpStorm 2018.3 Help

Finding Unused Code with Coverage

PhpStorm lets you find unused JavaScript, TypeScript, and CSS code in your client-side applications. When you run an application in the special Code Coverage mode, PhpStorm creates a report showing how much code in every file and folder was used. Thanks to source maps, this report shows coverage for your source files but not for the compiled code that was actually run in the browser.

To run an application in the Code Coverage mode

  1. Create a run/debug configuration of the type JavaScript Debug:
    Choose Run | Edit Configuration on the main menu, click icons general add on the toolbar and select JavaScript Debug from the pop-up list. In the Run/Debug Configuration: JavaScript Debug dialog that opens, specify the URL address at which the application is running. This URL can be copied from the address bar of your browser.

    JavaScript Debug configuration
    Click OK to save the configuration settings.

  2. Choose the newly created configuration in the Select run/debug configuration drop-down list on the toolbar and click icons general runWithCoverage svg next to the list.

    ws javascript coverage run with coverage
    The URL address specified in the run configuration opens in the browser.

  3. To learn what code was executed during the page load, just load the application and then stop it by clicking artwork studio icons shell toolbar stop on the toolbar, next to icons general runWithCoverage svg, or in the Run tool window. If you need a coverage report for some specific features of your application, trigger these features in the browser and only then click artwork studio icons shell toolbar stop to stop the application.

  4. View the report in the Coverage tool window. The Project tool window shows information about the coverage of files and folders. In the editor, the left gutter shows green markers next to the lines that were executed and red markers next to those that were not. You can also hover over the line markers and see how many times each line of code was hit.

    ws javescript coverage report with editor

Last modified: 18 March 2019