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

get-json-patches

v1.0.17

Published

A function to compare two js objects and return a collection of json patches from the differences

Downloads

18

Readme

GitHub Workflow Status npm

Statements Branches Functions Lines

npm bundle size GitHub

Package ships both CommonJs .cjs for use with require and EsModule .mjs for use with import.

Install

npm install get-json-patches

How To Use

import getJsonPatches from 'get-json-patches';

const obj1 = { s: 'string', n: 345.21, b: true, o: {s: 'string'}, a: [1,2,3]}
const obj2 = { s: 'string', n: 345.64, b: false, o: {s: 'new'}, a: [1,2], aNew: 'new prop'}

const patches = getJsonPatches(obj1, obj2);
/*
patches =
[
    {"op":"replace","path":"/n","value":345.64},
    {"op":"replace","path":"/b","value":false},
    {"op":"replace","path":"/o/s","value":"new"},
    {"op":"replace","path":"/a","value":[1,2]},
    {"op":"add","path":"/aNew","value":"new prop"}
]
*/

For additional use case scenarios you can look over the unit tests.

Motivation

I needed a simple way to generate a list of patch objects from comparing 2 javascript objects. Preferably to use in the browser on the client machine to prevent having to send a complete json object to a server for comparison and then to a db or api to apply partial updates. There are many javascript libraries that implement json patch, many of which are listed at jsonpatch.com. Some existing libraries offer a diff function to construct collection of patch objects but this seams like a additional after thought to many libs and therefore they are large libs that implement all parts of the json patch spec. Many API's including Azure Cosmos Db expect a json patch and can implement partial updates. This lib just does object comparison and patch creation.

TODO List

  • [X] Implement replace primitives
  • [X] Implement replace objects
  • [X] Implement replace arrays
  • [X] Implement add object
  • [X] Implement add arrays
  • [ ] Add RFC spec path substitutes
  • [ ] Implement remove in array
  • [ ] Implement append to array with - in path
  • Currently the array functionality will just replace entire array if array lengths differ and will only iterate array when lengths are the same.

  • [ ] rfc6901 pointer should be '' rather then '/' to point at root

Notes

For array comparisons the length of the arrays are compared first and if different then the entire array is replaced at the path. If array lengths are the same, we loop over the array comparing the value at same index from first array with second array. If values are different then a set op patch will be returned at /arrayPath/<index> path.