Security Fix for Prototype Pollution - huntr.dev #262

Use ES6 Modules

• package now exports non-bundled ES module #232
• main still points to CommonJS module for backward compatibility
• README recommends use of named ES imports

List of changes
v2.2.1...3.0.0-0

• package now exports non-bundled ES module #232
• main still points to CommonJS module for backward compatibility
• README recommends use of named ES imports

Full list of changes
v2.2.1...3.0.0-0

This patch release fixes a regression introduced in 2.2.0, namely: the default import using ES6 with Webpack/Babel stopped working (#233).

This version fixes the problem by adding an explicit default import.

New feature:

• Ability to generate test operations for original values in the first object, also known as "invertible" operations. Search fro the word invertible in README.md for details about usage (PR #228, PR #226).

Code quality:

• Replace deep-equal with fast-deep-equal (PR #227)
• Remove traces for support for legacy browsers which were broken since v2.0.7 (PR #229)
• Fix testing framework

• applyOperation and applyReducer now accept an optional index parameter. This param is used to create more elaborate error messages when invalid operations occur in your patches, #221.

• Error messages are now nicely-formatted, they look like:

	The specified index MUST NOT be greater than the number of elements in the array
    name: OPERATION_VALUE_OUT_OF_BOUNDS
    index: 1
    operation: {
      "op": "add",
      "path": "/root/1",
      "value": "val"
    }
    tree: {
      "root": []
    }"

• By default, prototype injection is not allowed and throws an error. If you want to pollute a prototype, you'll need to pass a flag banPrototypeModifications = false to all applyX functions. #219.
• Bad behaviour when you replace an object with an array is now fixed. See #205.

Performance improvements:

add op: 117% faster
remove op: 109% faster
replace: 112% faster
test: 131%
geneate: 110% faster

IE11 support is still 10/10.

IE versions lower than 11 are not supported anymore.

See #208 & #212

• Ignore tsconfig.json when publishing to NPM 5236d81, thanks @LinusU!
• add param mutateDocument in function applyPatch that defaults to true. If you set it to false, your object will be cloned before applying any operations. 688be37, thanks @chochihim!

Earlier, setting array props wasn't possible:

var obj = [];
jsonpatch.applyPatch(obj, [{op: 'add', path: '/prop', value: 'arrayProp'}])
console.log(obj.prop); // --> undefined

Now it is.

• Validate on applyPatch when validation is enabled (fix #186)