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

mock-stdio

v1.0.3

Published

mock stdio output for tests

Downloads

726

Readme

mock-stdio

travis cov-codeclimate gpa-codeclimate npm-downloads npm-version dm-david

This is just a simple module allowing you to easily test (or just ignore) code that needs to console.log or otherwise write to standard out and standard error.

Install

npm install --save-dev mock-stdio

Example

var mockIo = require('mock-stdio');
var expect = require('chai').expect;

describe('thing', function () {
  it('writes to standard out', function () {
    // Start the mock... it will not be possible to write to
    // the real stdout and stderr when this is active.
    mockIo.start();

    // Call your code.
    someFunction();

    // When you are done, end the mock, and it will return
    // all the data written to stdout and stderr while the mock
    // was active.
    var result = mockIo.end();

    // Make sure that what you expected was written to
    // the corresponding output.
    expect(result.stdout).to.be.a('string');
    expect(result.stderr).to.be.a('string');
  });
});

Note that it is best to use the mock directly inside the test, rather than in before or after functions, as it will not be possible for anything within the node process to log to stdout and stderr, meaning you may lose messages that are printed by your test framework.