nano-memoize - npm Package Compare versions

Comparing version 1.2.0 to 1.2.1

package.json

		{
		"name": "nano-memoize",
		"version": "v1.2.0",
		"version": "v1.2.1",
		"description": "Faster than fast, smaller than micro ... a nano speed and nano size memoizer.",
		"main": "index.js",
		"engines": {},
		@@ -6,0 +7,0 @@ "sideEffects": false,

README.md

		@@ -21,3 +21,3 @@ [![Codacy Badge](https://api.codacy.com/project/badge/Grade/30ce201484754fa5b0a6c6046abb842d)](https://www.codacy.com/app/syblackwell/nano-memoize?utm_source=github.com&utm_medium=referral&utm_content=anywhichway/nano-memoize&utm_campaign=Badge_Grade)

		The minified/brotli size is 789 bytes for `nano-memoize` v1.1.5 vs 1,356 bytes for `micro-memoize` v4.08. And, `nano-memoize` has
		The minified/brotli size is 789 bytes for `nano-memoize` v1.2.0 vs 1,356 bytes for `micro-memoize` v4.08. And, `nano-memoize` has
		slightly more functionality.
		@@ -216,3 +216,6 @@

		2020-11-02 v1.2.1 Added main: "index.js" reference in package.json.

		2020-06-18 v1.2.0 Enhanced multi-arg handling so that arg lengths must match precisely (thanks @amazingmarvin), unless `maxArgs` is passed as an option.
		Also added `callTimeout` to go ahead and call underlying function to ensure callbacks are invoked if necessary.

		@@ -219,0 +222,0 @@ 2020-05-26 v1.1.11 [Fixed Issue 17]Fixed https://github.com/anywhichway/nano-memoize/issues/17. It is not known when this bug made its way into the code.

New alerts