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

diff-seq

v0.1.0

Published

a recursive diff of javascript sequentiable data structures

Downloads

2

Readme

README

Recursive diffing algorithm on JavaScript Arrays and Plain Objects.

Rationale

Inspired by Clojure's data/diff module from here.

Data in JavaScript is frequently stored in Arrays / Objects and it may be useful to be able to diff them. This is what this module provides.

Installation & usage

npm install data-diff Note : waiting to be published on npm

You use it by passing two versions of a same "model", it will return an object with three keys :

  • previous : keys / values only presents in the "previous" version
  • same : keys / values presents in both versions
  • next : keys / values presents in the next version

The value null is used when no correspondances are found between the two.

Example 1

With objects sharing keys

const { diff } = require("data-diff")

const d1 = {
    a: 1,
    b: 2,
    c: 3
}
const d2 = {
    a: 3,
    b: 2,
    d: 4
};

const { previous, same, next } = diff(d1, d2);


/*
values only found in
previous = {
    a: 1,
    c: 3
}
same = {
    b: 2
}
next = {
    a: 3,
    d: 4
}

*/

Example 2

With objects not sharing keys

const d1 = {
    a: 1
};
const d2 = {
    b: 1
};
const {previous, same, next} = diff(d1, d2);

/**
previous = { a: 1 }
same = null
next = { b: 1 }
**/

Example 3

With arrays

const d1 = [1, 2];
const d2 = [3, 2];

const {previous, same, next} = diff(d1, d2);
/**
previous = [1, undefined];
same = [undefined, 2];
next = [3, undefined];

**/

Todo

  • migrate tests from tape to mocha
  • add supports for Maps/WeakMaps and Sets/WeakSets
  • provide an high-level api to add support for custom data structure.
  • provide minified build for use in the browser with source maps and co.
  • provide an example of React Component wrapping MVC libraries using diffing pattern (Google Maps and Highcharts are the primary targets of this effort).

Warning

This package supports diffing sequential data structures but does not offer guarantees as to what objects are returned. It may (should, maybe) change in the future but if no differences are found between objects we do not guarantee that the structure returned is the original object.

This is the case because JavaScript does not support Immutable data structure and it would introduce subtle behaviour in the structures returned.

However you can easely know if a structure is contained in a another (or if they differ entirely) by testing for null in the keys returned, for instance :

  • same === null means that there is no key sharing between the structures
  • previous === null means that it is entirely contained inside the next one (respectively next === null).

There is an exception though when both of the structures are empty. In this case all {same, previous, next} are null.