new-error - npm Package Compare versions

Comparing version 1.1.1 to 1.1.2

CHANGELOG.md

		@@ -0,1 +1,7 @@
		## 1.1.2 - Mon Sep 21 2020 04:13:44

		Contributor: Theo Gravity

		- Fix README.md

		## 1.1.1 - Mon Sep 21 2020 03:57:31
		@@ -6,2 +12,4 @@
		- Add deserialization support (#7)
		- Include `logLevel` as part of `toJSON()`
		- Fix interface definitions and examples

		@@ -8,0 +16,0 @@ Please read the README section on the limitations and security issues relating to deserialization.

package.json

		{
		"name": "new-error",
		"version": "1.1.1",
		"version": "1.1.2",
		"description": "A production-grade error creation and serialization library designed for Typescript",
		@@ -5,0 +5,0 @@ "main": "build/index.js",

README.md

		@@ -57,3 +57,3 @@ # new-error
		- [Deserialization is not perfect](#deserialization-is-not-perfect)
		- [potential security issues with deserialization:](#potential-security-issues-with-deserialization)
		- [Potential security issues with deserialization](#potential-security-issues-with-deserialization)
		- [`ErrorRegistry#fromJSON()` method](#errorregistryfromjson-method)
		@@ -673,3 +673,3 @@ - [`static BaseError#fromJSON()` method](#static-baseerrorfromjson-method)

		### potential security issues with deserialization:
		### Potential security issues with deserialization

		@@ -743,3 +743,3 @@ - You need to be able to trust the data you're deserializing as the serialized data can be modified in various ways by
		// err should be an instance of InternalServerError
		const err = errRegistry.toJSON(data, {
		const err = errRegistry.fromJSON(data, {
		safeMetadataFields: {
		@@ -746,0 +746,0 @@ safeData: true

New alerts