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

lawyered

v0.1.1

Published

A simple module to implement design by contract in node.js

Downloads

17

Readme

lawyered.js

A simple lightweight module that allows design by contract.

Installing

npm install lawyered

Summary

This module allows you to run code before and after your methods, giving you the possibility to verify that certain conditions are met. The module relies on conventions to determine which methods should be run as pre/post conditions for a particular method.

  • Preconditions methods are expected to append "_pre" to the name of the original method.
  • Postconditions methods are expected to append "_post" to the name of the original method.
  • The invariant method should be named "_invariant".

Simple cases

var law = require('lawyered');
var Assert = require('assert');

var value = 0;

var o = law.instrument({
    m_pre: function(){
        Assert.equal(value, 0);
    },
    m: function(){
        value++;
    },
    m_post: function(){
        Assert.equal(value, 1);
    },
});

o.m();

Complete scenario

Features:

  • All methods (pre, original and post) receive original method parameters.
  • Post condition methods receives value returned from original method as last parameter.
  • The invariant method runs after every method. It is invoked after the postcondition or the method itself if the method does not have a postcondition.
"use strict";

var law = require('lawyered');
var Assert = require('assert');

var value = 0;

var positiveNumberAdder = {
    total: 0,
    add_pre: function(a, b){
        Assert.ok(a > 0);
        Assert.ok(b > 0);
    },
    add: function(a, b){
        var partial = a + b;
        this.total = partial;
        return partial;
    },
    add_post: function(a, b, returnValue){
        Assert.ok(returnValue > a);
        Assert.ok(returnValue > b);
        Assert.equal(a + b, returnValue);
    },
    _invariant: function(){
        Assert.ok(this.total > 0);
    }
};

law.instrument(positiveNumberAdder);

console.log(positiveNumberAdder.add(10, 15)); // outputs 25
console.log(positiveNumberAdder.add(1, 2)); // outputs 3

Inspiration