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

contracted

v0.0.4

Published

Small & focused contract library to ensure expectations are met!

Downloads

25

Readme

contracted

NPM Version

About

There are many situations where explicit expectations help stability and make integrations easier. Any sort of library that can interact with multiple drivers (e.g. Dropbox, S3, Drive, etc.) can benefit from explicitly stating the expectations of implemenations. In Java & PHP for example, they have builtin interfaces which are used to express expectations. JS core lacks the notiion of interfaces - this lib tries to fill that hole!

One specific use case for contracts is the npm lib, cacheman. There are multiple drivers (redis, mongodb, memory) for caching and the core lib expects the drivers to implement specific methods. The author implements his own checking of the drivers to ensure the expected methods exists.

Install

npm install contracted

Example

'use strict';

const Contracted = require('contracted');
const Integration = require('./integration');

const contract = new Contracted();

// What are the terms we expect to be fullfilled?
contract.addTerms('StorageHandler', {
   'save->string' : ['name:string', 'callback?'],
   'get->Promise'  : 'name:string' // can also be ['name:string']
});

// Example class using contracted
class Storage {
    constructor(contract) {
        this.contract = contract;
        this.drivers = {};
        this.driver = null;
    }

    use(Integration) {
        // Does the integration meet our contract expectations?
        this.contract.agreement('StorageHandler', Integration);
        this.drivers[Integration.name] = new Integration(this);
    }

    // ... get, etc
}

// You can also get down & fancy with ES7 decorators
@contract.arguments('string', 'function?')
function save(name, callback) {
    // ...
}

License

MIT