npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

cleaner-node

v1.3.1

Published

Helpful utilities and scripts to make Node projects more legible and easier for the next developer to take over.

Downloads

61

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

fredlackeyfredlackey

Keywords

nodenodejscleancleancodeutilsutilityutilitieslodashalternativeunderscorealternativeterraformhcl

Readme

Cleaner Node (cleaner-node)

Helpful utilities and scripts to make Node projects more legible and easier for the next developer to take over.

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, 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 maintain. 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

v0.0.1 - v0.22.2

The first iteration of cleaner-node proved to be very successful. It was used in several projects and was great at reducing the noise in the codebase. It actually lead to the development of other projects, such as restutils-host and restutils-client; tools that allow instant API creation from any JavaScript file or Node package. During this time there was experimentation with both CommonJS and JavaScript Modules. It was decided that, while JavaScript Modules are the future, CommonJS is still the standard for Node projects and will be for some time. As such, the first release of cleaner-node will be in CommonJS with other projects, such as nextjs-helpers, focusing on JavaScript Modules.

v1.0.0

The first actual release of cleaner-node, this version focuses on reducing code complexity for common tasks within Node projects. It is written using CommonJS and is intended to be used in Node projects. It is not intended to be used in the browser, though it may work in some cases. It is also not intended to be used in React projects, though it may work in some cases.

Contact

If you have any questions, comments, or concerns, please feel free to reach out to me at...

Fred Lackey
[email protected]
http://fredlackey.com