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

node-test-helpers

v1.0.0

Published

node-test-helpers =================

Downloads

2

Readme

node-test-helpers

My node test helpers

// Usage: var TH = require('node-test-helpers')(module, [contraLogOptions]);

// You have a contra log object // But by default, the logger is off (don't want logging in your tests unless you are debugging) // so if this wont display: TH.cl.trace('This %s %s console log msg', 'is', 'a');

// Turn it on: TH.cl.on(); // And now you have logging: TH.cl.trace('This %s %s console log msg', 'is', 'a');

// Using Lab? TH.register.Lab();

// Now you have lab versions of describe/it/before*/after*, and chai.expect, chai-promised, sinon, sinon-chai describe('foo', function(){ it('is', function(done){ expect(true).to.be.true; done(); }) });

// Want to add some test data (just a convenience method: TH.register.data({some:'data'});

// And some utilities for logging and stubs (based on bluebird and sinon); // Lets say you want to stub fs.readFile: var BluebirdPromise = require('bluebird'); var Fs = Promise.promisifyAll(require("fs")); // You now have: Fs.readFileAsync('file.txt', 'utf8');

// You can now stub and trace it with:

var stub = sinon.stub( Fs, 'readFileAsync', TH.UTILS.createAsyncStub('createAsync', 'contents of stubbed file call') );

// Now whenever you call Fs.readFileAsync(any, parameters); // You will see (assuming contralog is on): [LOGLOC] ------------------------------------------------------------------------ [LOGLOC] *** STUB INTERCEPT: readFileAsync [LOGLOC] *** PARAMETERS: [LOGLOC] *** RETURNING: [LOGLOC] ------------------------------------------------------------------------