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

covwatcher-client

v1.9.0

Published

Client for the covwatcher server. Used to upload reports.

Downloads

5

Readme

covwatcher-client

codecov CircleCI npm

Client module for Covwatcher

Installation

Install the client in your target repo

npm install covwatcher-client

Documentation

The client is available as executeable covwatcher and can upload reports via commandline parameters or environment variables:

| shorthand | long version | description | environment variable | required | | :-------: | :----------: | :---------------------------------------------------- | ----------------------: | :------: | | -n | --name | name of the branch or if this is a pullrequest its id | COVWATCHER_BRANCH_NAME | * | | -t | --target | branchtype, can be "branch" or "pullrequest" | COVWATCHER_BRANCH_TYPE | * | | -y | --type | repository type, can be "users" or "project" | COVWATCHER_REPO_TYPE | * | | -p | --project | name of the project or user the repository is part of | COVWATCHER_REPO_PROJECT | * | | -r | --repo | name of the repository | COVWATCHER_REPO | * | | -s | --server | full url to the server running covwatcher | COVWATCHER_SERVER | * | | -d | --directory | full path to the coverage report | COVWATCHER_REPORT | | | -a | --task | wether to create a task if the diff coverage is low | | | | -l | --lcov | full url to the server hosting the lcov report | | | | -b | --bail | whether to return nonnull status on failure | | | | -h | --help | usage information | | |

The command covwatcher -n "master" -t "branch" -y "users" -p "Fochlac" -r "covwatcher" -s "http://covwatcher.fochlac.com" will start a search for the closest coverage file and upload it to the specified server. The search will start from the location of this package, so it should always be installed in the specific repository you want searched or you should provide the full path to the report via the -d option.

Changelog

License

ISC License