npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

covered

v1.1.2

Published

Covered code extraction for Chrome code coverage report

Downloads

15

Readme

Covered code extractor for Chrome

Chrome 73 now supports export of code coverage report available since Chrome 59. export button in Chrome 73

Usage

This npm package allows you to extract portions of the code that were executed during the session.

All you need to do is to save coverage report as JSON file and execute the following command using npx.

npx covered report.json

Command outputs a list of assets and generated covered files as well as percentage of the original file used. command output

Script generates two folders with all the assets used in the session saved as files.

One folder, report_original/ will contain original content of the files, served to the browser.

Another, report_covered/ will contain only code that was actually executed.

Caveats

Keep in mind that code inside HTML files contains a mix of JavaScript and CSS instructions.

Extracted JavaScript code can not necessarily be used as is (CSS code seems to be good), following issues are known:

  • anonymous functions that are not included and passed as arguments to other functions as empty