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

vows

v0.8.3

Published

Asynchronous BDD & continuous integration for node.js

Downloads

207,159

Readme

vows Build Status

Asynchronous BDD & continuous integration for node.js

http://vowsjs.org

introduction

There are two reasons why we might want asynchronous testing. The first, and obvious reason is that node.js is asynchronous, and therefore our tests need to be. The second reason is to make test suites which target I/O libraries run much faster.

Vows is an experiment in making this possible, while adding a minimum of overhead.

synopsis

var vows = require('vows'),
    assert = require('assert');

vows.describe('Deep Thought').addBatch({
    'An instance of DeepThought': {
        topic: new DeepThought,

        'should know the answer to the ultimate question of life': function (deepThought) {
            assert.equal (deepThought.question('what is the answer to the universe?'), 42);
        }
    }
});

coverage reporting

Code coverage reporting is available if instrumented code is detected. Currently only instrumentation via node-jscoverage is supported. When instrumented code is detected and coverage reporting is enabled using any of the --cover-plain, --cover-html, or --cover-json options a code coverage map is generated.

downloading and installing node-jscoverage

node-jscoverage is a binary package that needs to be compiled from source:

$ git clone https://github.com/visionmedia/node-jscoverage.git
$ cd node-jscoverage/
$ ./configure
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
[...]
$ make && sudo make install

instrumenting with jscoverage

$ jscoverage myfile.js myfile-instrumented.js

installation

$ npm install vows

documentation

Head over to http://vowsjs.org

run tests

$ npm test

authors

Alexis Sellier, Charlie Robbins, Jerry Sievert

...and many others