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

test-watcher-tdd

v0.0.4

Published

A lightweight un-opinionated watcher which will execute unit tests when either the test or module file changes. Test driven development is the way to go!

Downloads

2

Readme

test-watcher-tdd

A lightweight un-opinionated watcher which will execute unit tests when either the test or module file changes. Test driven development is the way to go!

Setup

npm install --save-dev test-watcher-tdd

Create your test watcher config file .test-watcher-tdd.js in your project root.

// simple example for mocha (you must have mocha installed)
module.exports = {
  style: 'relative', // our test files are relatively located to the module files
  testFileSuffix: '-test', // x.js would have a test file called x-test.js
  testsDirName: '_tests', // foo/bar/x.js would have a test file foo/bar/_tests/x-test.js
  runner: 'mocha', // use the provided "mocha" runner (or your own implementation as a function)
  params: ['-R', 'spec'] // additional parameters to be included when the test is run
};

Running the watcher

As long as you have node_modules/.bin in your path

test-watcher-tdd

that's it!

Configuration Options

You can use a custom file handler (thing that associates test files with module files) but default handler is robust. Use the fileHandler option to provide your own (more details below).

  • style: relative for test files relative to the module file or N/A for test files in a separate directory
  • testsDirName: if relative style then the relative dir name for tests; otherwise the directory under the project root for tests
  • testFilePrefix: optional prefix for test files; x.js with prefix of test- would have a test file of test-x.js
  • testFileSuffix: optional suffix for test files; x.js with suffix of test- would have a test file of x-test.js
  • runner: mocha or a custom implementation (more details below)
  • params: array of any additional parameters for the test execution
  • fileHandler: optional custom function that associates module files with unit test files (usually the default handler will suit your needs)