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

@abinavseelan/papers-please

v0.2.1-beta.0

Published

jest-based test case mandating tool for new code

Downloads

12

Readme

papers-please

All Contributors

jest-based test case mandating tool for new code.

Install

npm install -D papers-please

Requires Node 8+ and Jest 25.x+

⚠️ For coverage reporting, Jest coverage needs be be collected as json-summary.

// In jest.config.js

{
  coverageReporters: ["json-summary"]
}

Usage

CLI

npx papers-please --trackGlobs="<comma separated list of file globs to track>" --baseBranch="<branch to check file diff against>"

Example

npx papers-please --trackGlobs="**/src/**/*.js,**/client/**/*.js,**/server/**/*.js" --baseBranch="main"

As an npm script

// In your package.json

{
  "scripts": {
    "validate": "npx papers-please --trackGlobs="**/src/**/*.js,**/client/**/*.js,**/server/**/*.js" --baseBranch="main""
  }
}

As a git hook

papers-please can be used alongside husky to run validation on git commit and / or git push.

Options

| Option | Type | Description | Default Value | |------------------------------|---------|--------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------| | --baseBranch | string | Base branch to validate your branch against to derive new and modified files | origin/main | | --projectRoot | string | Root directory for the project. Assume this to be where the .git folder resides | process.cwd() | | --coverageFile | string | Path to the jest coverage report. Note The coverage summary report should be the json summary output | ./coverage/coverage-summary.json | | --skipCoverage | boolean | Skip coverage metrics validation | false | | --trackGlobs | string | List of comma-separated source files / globs to track. Any file that is modified or added that matches the glob pattern will be validated. | */ | | --branchCoverageThreshold | number | Branch coverage threshold for new files (in percentage) | 80 | | --functionCoverageThreshold | number | Function coverage threshold for new files (in percentage) | 80 | | --lineCoverageThreshold | number | Line coverage threshold for new files (in percentage) | 80 | | --statementCoverageThreshold | number | Statement coverage threshold for new files (in percentage) | 80 | | --help | boolean | Show usage and available options | false | | --verbose | boolean | Show verbose output for each step | false | | --exposeMetrics | boolean | Exposes coverage metrics into a json file for the modified/added files which matches the glob pattern | false |

Contributing

Want to fix something, add a new feature or raise an issue? Please read the contributing guide to get started. :smile:

Contributors ✨

Thanks goes to these wonderful people (emoji key):

This project follows the all-contributors specification. Contributions of any kind welcome!