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

with-sandbox

v1.0.0

Published

Mocha utility for sandboxing tests

Downloads

4

Readme

Test Coverage CircleCI

with-sandbox

Utility for sandboxing all of your mocha tests.

Tested on node v4.2.5-v5.10.1, v6.11.0, and v8.1.2.

Usage

Define your sandbox

config.js
const configureSandbox = require('with-sandbox');

module.exports.withSandbox = configureSandbox({
  create: function() {
    // return a sandbox object with any properties you want here
    // runs once before the block wrapped with `withSandbox`
    return {
      sinon: sinon.sandbox(),
    }
  },
  restore: function(sandbox) {
    // restore everything on the sandbox
    // runs after every test in the block wrapped with `withSandbox`
    sandbox.sinon.restore();
  }
});

Use your sandbox

test.js
const withSandbox = require('./config.js');

describe('Some test', withSandbox(function(sandbox) {
  beforeEach(function() {
    // you can now access your sandbox
    // your sandbox will be restored after each test in the block
  });
}));

Why not use before and afterEach?

Some people create sandboxes like this:

before(() => {
  this.sandbox = { sinon: sinon.sandbox.create() };
});

afterEach(() => {
  this.sandbox.sinon.restore();
});

This does not allow you to access the sandbox everywhere you might want to:

describe('someTest', function() {
  // These will not work
  def('myFunc', () => this.sandbox.sinon.stub()); // bdd-lazy-var
  let myFunc = this.sandbox.sinon.stub(); 
});

withSandbox allows you to access the sandbox more easily:

describe('something', withSandbox(function(sandbox) {
  // These will both work
  def('myFunc', () => sandbox.sinon.stub()); // bdd-lazy-var
  let myFunc = sandbox.sinon.stub(); 
}));