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

json8-merge-patch-to-patch

v1.0.6

Published

Turn JSON Merge Patch into JSON Patch.

Downloads

7

Readme

JSON8 Merge Patch To Patch

Turn JSON Merge Patch into JSON Patch.

JSON Patch is a more capable alternative to JSON Merge Patch. To work with JSON Patch see JSON8 Patch.


npm install json8-merge-patch-to-patch


const mergePatchToPatch = require("json8-merge-patch-to-patch");

Does not validate the merge patch nor the patch for JSON correctness, use JSON8 valid.


const JSONMergePatch = {
  foo: { bar: "foobar" },
  bar: null,
};
const JSONPatch = mergePatchToPatch(JSONMergePatch);
/*
[
  { op: 'add', path: '/foo/bar', value: 'foobar' },
  { op: 'remove', path: '/bar' }
]
*/

Per specification a JSON Merge Patch that would successfully apply on a document might fail to apply once converted to a JSON Patch.

There are 3 cases:

Incompatible destination

const doc = [];
const JSONMergePatch = { a: "hello" };
const JSONPatch = mergePatchToPatch(JSONMergePatch);
// JSONPatch will fail to apply because doc is not an object

Wrong location

const doc = {};
const JSONMergePatch = { a: { b: "hello" } };
const JSONPatch = mergePatchToPatch(JSONMergePatch);
// JSONPatch will fail to apply because doc.a doesn't exist

Remove non-existant value

const doc = {};
const JSONMergePatch = { a: null };
const JSONPatch = mergePatchToPatch(JSONMergePatch);
// JSONPatch will fail to apply because doc.a doesn't exist

An option could be added to produce a successful JSON Patch no matter what but the only way to do this is to pass the document as well. Let me know if there is any interest or contribute.