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

interfacejs

v0.0.1

Published

Simple interfaces for complicated code

Downloads

3

Readme

interfacejs

Define and enforce module interfaces

Install

npm install interfacejs

Usage

We use this by defining an interface in its own file: interfaces/cdn.coffee

module.exports = {
  load: true,
  save: true,
  exists: true
}

Then some file that wants to do stuff with a cdn can require a dependency that meets this interface:

module.exports = interfacejs(require('../interfaces/cdn'), function (cdn) {
  return {
    getFile: function (name, cb) {
      cdn.load(name, cb)
    }
  }
})

in coffeescript:

module.exports = interfacejs require('../interfaces/cdn'), (cdn) ->
  getFile: (name, cb) ->
    cdn.load name, cb

Now there can be many different implementations of cdn, something like:

// this could be made to hit any cdn
module.exports = function (cdnUser, cdnPass) {
  return {
    load: function () {
      // do stuff for loading a file
    },
    save: function () {
      // do stuff for saving a file
    },
    exists: function () {
      // do stuff to check if file exists
    }
  }
}

When someone wants to use our module that uses a cdn, just pass in our preferred cdn:

cdn = require("./cdns/s3")("me", "gusta")
module = require("./module")(cdn)

module.getFile(...)

Running Tests

npm install -g mocha mocha test.js