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 🙏

© 2026 – Pkg Stats / Ryan Hefner

divergence

v1.0.0

Published

Calculates and applies the divergence between 2 objects

Readme

divergence

Calculates and applies the divergence between 2 objects

Install

npm install divergence

Usage

Calculate

var oldObject = {
        a: {
            foo: 'bar'
        },
        b: {
            meh: 'stuff'
        },
        c: {
            things: 'majigger'
        }
    },
    currentObject = {
        b: {
            meh: 'moar stuff'
        },
        c: {
            things: 'majigger'
        },
        d: {
            beep: 'boop'
        }
    };

calculate(oldObject, currentObject);

// {
//     "a":[0],
//     "b.meh":[1,"moar stuff"],
//     "d":[2,{"beep":"boop"}]
// }

Apply

var oldObject = {
        a: {
            foo: 'bar'
        },
        b: {
            meh: 'stuff'
        },
        c: {
            things: 'majigger'
        }
    },
    currentObject = {
        b: {
            meh: 'moar stuff'
        },
        c: {
            things: 'majigger'
        },
        d: {
            beep: 'boop'
        }
    },
    diff = calculate(oldObject, currentObject); //{"a":[0],"b.meh":[1,"moar stuff"],"d":[2,{"beep":"boop"}]}

apply(oldObject, diff);

deepEqual(oldObject, currentObject); // Objects are equal

Diff output format

The output format of a diff is designed to be minimal and not necessarily human readable.

However if you want it can be inflated.

The keys of the diff object are dot separated keys of the original object that have been changed.

The value of the key is an array, where the first item is the action that occurred and the second is the new value.

Actions are defined as:

deleted: 0
modified: 1
added: 2

For example:

a diff object of

{
    "a":[0],
    "b.meh":[1,"moar stuff"],
    "d":[2,{"beep":"boop"}]
}

Means that the key a was deleted, b.meh was modified to be "moar stuff" and d was added with the value of {"beep":"boop"}

#Arrays

This module will totaly work with arrays, however it currently does not handle deletions very efficiently.

For example:

var oldObject = [0,1,2,3,4,5],
    currentObject = [1,2,3,4,5],
    diff = calculate(oldObject, currentObject);

Should result in:

{
    '0': [ 0 ]
}

But will result in:

{
    '0': [ 1, 1 ],
    '1': [ 1, 2 ],
    '2': [ 1, 3 ],
    '3': [ 1, 4 ],
    '4': [ 1, 5 ],
    '5': [ 0 ]
}

The final applied result will be the same, however will take longer / has more to process

This will get fixed at some stage and is currently tracked in issue #1