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

implements-interface

v0.0.7

Published

Tests whether an object has the same methods and signatures defined by a prototype.

Readme

implements-interface

A function that tests whether or not an object implements an interface defined by a prototype.

There are some important caveats. It does not work reliably when testing against functions that evaluate to:

  • Native functions: As far as I know, it isn't possible to get the arguments from a native function so always return an empty set. Depending on whether your interface method has arguments or not, you will either get a false positive or a false negative.
  • Bound functions: If you bind a function, e.g. const bar = foo.bind(this), the returned function (in this case, bar) turns out to be native and has the same drawbacks.

Installing

npm install --save-dev implements-interface

Getting Started

Import the library, define your interface as a regular JavaScript class, and simply call implementsInterface with the object to test and the interface (class), e.g.:

import { implementsInterface } from 'implements-interface'

class FooBarInterface {
  foo (x, y) { }
  bar (z, ...rest) { }
}

const passingObj = {
  foo (a, b) {
    // arbitrary implementation
  },
  bar (a, ...more) {
    // arbitrary implementation
  }
}

const failingObj = {
  foo (a, b, c) {
    // arbitrary implementation
  },
  bar (a, ...more) {
    // arbitrary implementation
  }
}

try {
  console.log(implementsInterface(passingObj, FooBarInterface)) // returns true
  console.log(implementsInterface(failingObj, FooBarInterface)) // throws Error
} catch (e) {
  console.log(e)
}

You can use this as a basis for a matcher in a testing framework, for example, with jest, a matcher might be defined and used like this:

/* global test, expect */
import { implementsInterface } from 'implements-interface'

expect.extend({
  toImplement (object, Interface) {
    try {
      implementsInterface(object, Interface)
      return {
        message: () => `expected object not to implement ${Interface.name}.`,
        pass: true
      }
    } catch (e) {
      return {
        message: () => e.message,
        pass: false
      }
    }
  }
})

class FooBarInterface {
  foo (x, y) { }
  bar (z, ...rest) { }
}

test('successfully implementing the FooBarInterface', () => {
  const object = {
    foo (a, b) {
      // arbitrary implementation
    },
    bar (a, ...more) {
      // arbitrary implementation
    }
  }

  expect(new FooBarInterface()).toImplement(FooBarInterface)
  expect(object).toImplement(FooBarInterface)
})

test('improperly implementing the FooBarInterface', () => {
  const object = {
    foo (a, b) {
      // arbitrary implementation
    },
    bar (a, more) {
      // arbitrary implementation
    }
  }

  expect(object).not.toImplement(FooBarInterface)
})