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

grunt-lab

v2.1.4

Published

Use the Spumko Lab test utility in Grunt.

Downloads

25

Readme

grunt-lab Build Status

Dependencies Status DevDependencies Status PeerDependencies Status

Use the hapi.js lab test utility in Grunt.

Configuration

All configuration is optional. See the Lab documentation for more information about each parameter.

| grunt-lab option | Type | Default | Lab flag | | ---------------- | ------- | ------------------ | -------- | | files | [glob] | [ "test/**/*.js" ] | | | coverage | boolean | false | -c | | color | boolean | false | -C | | dryRun | boolean | false | -d | | nodeEnv | string | test | -e | | pattern | string | | -g | | global | boolean | false | -G | | identifier | string | | -i | | ignoreGlobals | string | | -I | | disableLeakDetection | boolean | false | -l | | timeout | integer | 2000 | -m | | reportFile | string | | -o | | parallel | boolean | false | -p | | reporter | string | console | -r | | silence | boolean | false | -s | | minCoverage | integer | | -t | | verbose | boolean | false | -v |

An example Gruntfile using grunt-lab may look like this:

"use strict";

module.exports = function (grunt) {

	grunt.initConfig({
		lab : {
			color       : true,
			coverage    : true,
			minCoverage : 100
		}
	});

	// Load plugins
	grunt.loadNpmTasks("grunt-lab");

	// Register tasks
	grunt.registerTask("default", [ "lab" ]);

};

It is not required to specify any configuration at all if you don't want to.

Contributing

There are only a few things to keep in mind when submitting a PR:

  1. linting and style guidelines are followed
  2. 100% test coverage
  3. all tests pass

Otherwise, the build will fail. :)