cleaner-node
Advanced tools
Comparing version 0.9.6 to 0.9.7
{ | ||
"name": "cleaner-node", | ||
"version": "0.9.6", | ||
"version": "0.9.7", | ||
"description": "Helpful utilities and scripts to make Node projects more legible and easier for the next developer to take over.", | ||
@@ -5,0 +5,0 @@ "main": "index.js", |
# cleaner-node | ||
Helpful utilities and scripts to make Node projects more legible and easier for the next developer to take over. | ||
## Changes | ||
## Background | ||
There are several libraries out there designed to make life easier for developers (`moment`, `lodash`, `underscore`, etc.). However, for the most part, the goals of those utilities are to *add on* to what Node and JavaScript bring to the table. And, as Node and JavaScript mature, these packages mature, developers find them to be less of a _neccessity_ and end up removing them. While `cleaner-node` is _also_ a helper package, and completely unnecessary, it's goal is to abstract some of the more redundant and verbose syntaxes. The end result is a codebase that still functions as it would _without_ `cleaner-node` but is easier to read -- and therefore *maintain* -- for other developers. Unlike those other libraries, which shrink over time, I intend on growing `cleaner-node` for as long as Node exists so that I don't have to write the same code again, and again, and again, and again, and ag.... | ||
## Installation | ||
`npm i cleaner-node` | ||
## Changes | ||
| Version | Date | Description | | ||
@@ -7,0 +14,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
74595
51