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

guardian-runner

v0.0.5

Published

Node console runner for guardianjs micro testing framework.

Downloads

3

Readme

guardian-runner

Node console runner for guardianjs micro testing framework. The runner will watch for file changes and in the event of a change will run a test file. The assumption it makes is that you have a single test file to run which will report its result to the console.

Install

$ npm install guardian-runner

Usage

$ node_modules/guardian-runner start

By default this will run test.js and watch for file changes with a default matching the glob pattern of ['*.js', '**/*.js'] (except node_modules folder) which can be overridden with the following:

$ node_modules/guardian-runner start [testfile] [globpatterns]...

Or require the runner in code to make your own watch/runner.

var runner = require('guardian-runner');
runner('myguardiantests.js', ['source/**/*.js', '!source/build/*']);