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

coverage-svg

v0.0.3

Published

coverage % tag as svg generated for istambul unit test coverage provider

Downloads

86

Readme

coverage-svg reporter for istambul provider

Coverage % tag as svg generated for istambul unit test coverage provider.

git GitHub NPM version coverage

This reporter generates the coverage.svg file in directories next to index.html with least % from

  • Statement
  • Branch
  • Functions
  • Lines

vitest config sample

export default {
    test: {
        coverage: {
            reporter: ['text', 'json', 'html','coverage-svg'],
            provider: 'istanbul'
        }
    }
}

Use in README.md

The SVG should be available either in the repo or on CDN in order to be shown in GitHub page.

As unpkg.com reflects the npm content, where the coverage usually is not included, it can be done by publishing either test project with coverage results or the coverage content alone.

The good example would be a test project for custom-element.

coverage explainer

Often there is a need to generate the coverage not only for essential sources but also for complimentary code like mocks, StoryBook, etc. That impacts the total stats and do not have the interest to the consumer. The coverage-svg generates the SVG on each module and folder which you can refer individually. In this case the coverage for test-proj/coverage/src/package2 is published on

https://unpkg.com/[email protected] and the generated image is

https://unpkg.com/[email protected]/test-proj/coverage/src/package2/coverage.svg

change on release/ npm publish

The unpkg.com keeps each version of released package. You would need to update the URLs before release.