Comparing version 0.2.0 to 1.0.0
@@ -1,11 +0,9 @@ | ||
# 0.2.0 (2018-03-03) | ||
# 1.0.0 (2018-03-03) | ||
* Changed Node target version to 6 since it is the current LTS. | ||
* First official release is finally here! | ||
# 0.2.0 (2018-03-03) | ||
# 0.1.0 (2018-03-03) | ||
* Changed Node target version to 6 since it is the current LTS. | ||
# 0.0.11 | ||
@@ -12,0 +10,0 @@ |
{ | ||
"name": "freezly", | ||
"version": "0.2.0", | ||
"version": "1.0.0", | ||
"description": "Small utility for deeply freezing objects in JavaScript.", | ||
@@ -5,0 +5,0 @@ "main": "lib/index.js", |
@@ -29,2 +29,4 @@ # freezly [![NPM][npm-img]][npm-url] [![Coverage][cov-img]][cov-url] | ||
This project literally exports a single function which is used to deeply freeze any Javascript object. All nested arrays and objects become frozen, ensuring the entire object can't be mutated. This is primarily useful in functional programming, if you want to guarantee an object passed into a function isn't mutated by said function. However in practice deeply freezing objects comes with some amount of a performance cost so it is recommended to only deep freeze objects in a development environment and/or tests. | ||
Below is an example of how to use **freezly**. | ||
@@ -31,0 +33,0 @@ |
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
New author
Supply chain riskA new npm collaborator published a version of the package for the first time. New collaborators are usually benign additions to a project, but do indicate a change to the security surface area of a package.
Found 1 instance in 1 package
No v1
QualityPackage is not semver >=1. This means it is not stable and does not support ^ ranges.
Found 1 instance in 1 package
6143
0
64
0