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

classtubber

v0.0.1

Published

Stubs a class and returns references to methods on instances of said class

Downloads

3

Readme

classtubber

Stubs a class and returns references to methods on instances of said class

This is useful when stubbing a class before it's instanciated and you don't have access to it from the test itself. I would anticipate you'd usually use this with injectr/mockery/proxyquire.

class TestClass {
  testMethod() {
    // does something
  }
  anotherTestMethod() {
    // does something else
  }
}

[
  stubbedTestClass,
  stubReference,
] = createStubbedClass(TestClass, { testMethod: myCustomStub })

stubbedTestClass is now a stubbed function/class. When stubbedTestClass is instanciated it will modify the testclass property on the stubReference to be the instance.

All methods on the class will be stubbed. You can pass in your own stubs if you'd like specific behaviour. You can then access methods on the instance and assert against them. e.g. `expect(stubReference.testclass.testMethod).to.have.been.called()``

You can also make assertions against the class itself as that is a spy. This is useful for checking a class has been instanciated correctly. e.g. `expect(stubbedTestClass).to.have.been.calledWith({foo: 'bar'})``