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

sinonquire

v1.2.3

Published

Automatically stubs CommonJS modules returned by require() using Sinon.JS

Downloads

14

Readme

# sinonquire

Automatically stubs CommonJS modules returned by require/import using Sinon.JS

Inspired by Jest's "mock by default" concept.

Installation

npm install --save sinonquire

Usage

The following example uses mocha, chai and sinon-chai.

First, let's tell sinonquire which paths should never be loaded as stubs.

test/index.js:

import sinonquire from 'sinonquire';

sinonquire.excludePaths(
  '/node_modules/mocha/',
  '/my-app/test/'
);

Then, make sure this configuration module is started before all the tests. One way to do it is using the --require argument of mocha CLI.

package.json:

"scripts": {
  "test": "mocha --recursive --require ./test/index.js"
}

OK. Now suppose your app has two main modules, one is a class and the other is a function that instantiate the class a couple of times.

Based on this Jest example.

lib/User.js:

export default class User() {

  setName(name) {
    this.name = name;
  }

  getName() {
    return this.name;
  }

}

lib/createCouple.js:

import User from './User.js';

export default function createCouple(nameA, nameB) {
  const userA = new User();
  userA.setName(nameA);

  const userB = new User();
  userB.setName(nameB);

  return [userA, userB];
}

test/createCouple.js:

import {expect} from 'chai';
import sinonquire from 'sinonquire';

describe('createCouple', () => {

  let createCouple;

  beforeEach(() => {
    sinonquire.dontStub('../lib/createCouple.js');
    createCouple = require('../lib/createCouple.js');
  });

  afterEach(() => {
    sinonquire.resetStubs(); // needed for correct spying (eg. calls count)
  });

  it('should spy instance methods', () => {
    const couple = createCouple('userA', 'userB');
    expect(couple[0].setName).to.have.been.calledWith('userA');
    expect(couple[1].setName).to.have.been.calledWith('userB');
  });

  it('should stub instance methods', () => {
    const couple = createCouple('userA', 'userB');
    couple[0].getName.returns('something new');
    expect(couple[0].getName()).to.equal('something new');
  });

  it('should spy class instantiation', () => {
    createCouple('userA', 'userB');
    const User = require('../lib/User.js');
    expect(User).to.have.been.calledTwice;
    expect(User).to.have.been.calledWithNew;
  });

});