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 🙏

© 2025 – Pkg Stats / Ryan Hefner

mocha-mock

v1.2.1

Published

mock library for mocha

Readme

mocha-mock

Mock library for mochajs

Basically I wanted to avoid the call to mock.verify used in sinon

##Example

const assert = require('assert')
const {it, mock} = require('mocha-mock')

describe('Queue', () => {
  it('can peek', () => {
    const firstElement = 'firstElement'
    
    // The assertions added to the mock are run
    // automatically when the 'it' block is over.
    const linkedList = mock(new LinkedList([firstElement]))
      .shouldReceive('getHead')
      .once()
      .andReturn(firstElement)
      
    const queue = new Queue(linkedList)
    assert.equal(queue.peek(), firstElement)
  })
})

###API ####it returns an instance of mocha.it but will also run any assertions setup by mock during the it block

####mock returns an instance of MockObject

####MockObject.prototype.shouldReceive := (method: string) : MockObject asserts that the given method is called

####MockObject.prototype.once := () : MockObject

  • must be called after shouldReceive
  • asserts that the method used in shouldReceive should be called exactly once

####MockObject.prototype.twice := () : MockObject

  • must be called after shouldReceive
  • asserts that the method used in shouldReceive should be called exactly twice

####MockObject.prototype.times := (n: number) : MockObject

  • must be called after shouldReceive
  • asserts that the method used in shouldReceive should be called exactly n times

####MockObject.prototype.andReturn := (value: any) : MockObject

  • must be called after shouldReceive
  • sets the value to be returned for the method used in shouldReceive

####MockObject.prototype.with := (...args: any) : MockObject

  • must be called after shouldReceive
  • asserts that the method used in shouldReceive was called with the given args

####MockObject.prototype.verify := () : boolean

  • manually verify all of the assertions on the mock
  • returns true if all assertions pass
  • otherwise throws an an exception for the first assertion that failed