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

@build-chores/test

v0.9.0

Published

Testing JS projects is complicated.

Downloads

7

Readme

@build-chores/test

Testing JS projects is complicated.

Synopsis

License: GPL v3 npm version Build Status

Use your custom Babel configuration with the AVA test runner and instrument code coverage using nyc.

Usage

Install the @build-chores/test package into your project:

yarn install --dev @build-chores/test [email protected]

To make use of AVA add the following entry to your package.json. It will use your local .babelrc to compile your source code and use babel-plugin-istanbul to instrument the code. See the example package.json for a template.

{
  "ava": {
    "require": "@build-chores/test"
  }
}

ava is declared as a peer dependency. This means it has to be installed along the @build-chores/test package. Make sure to install either [email protected] or ava@next tag. The default ava package installs a very old version.

Configure code coverage by placing a .nycrc in your project root. See the example .nycrc for a template.

{
  "sourceMap": false,
  "instrument": true,
  "all": true,
  "include": [
    "src/**/*.js"
  ]
}

Please note that in order for all to work and instrument all source files, instrument has to be set to true.

Provide the test and coverage script targets to your package.json. AVA sets your NODE_ENV to test automatically. See the example package.json for a template.

{
  "scripts": {
    "test": "ava",
    "test:coverage": "nyc yarn test",
    "test:watch": "yarn test -w"
  }
}

You are ready to test your files.

Contribute

Check out our contributing.md to get started.

License