Why write a library?

This page summarizes the projects mentioned and recommended in the original post on dev.to

CodeRabbit: AI Code Reviews for Developers
Revolutionize your code reviews with AI. CodeRabbit offers PR summaries, code walkthroughs, 1-click suggestions, and AST-based analysis. Boost productivity and code quality across all major languages with each PR.
coderabbit.ai
featured
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
www.saashub.com
featured
  • scope-logger

    Trace a variable through function calls

    By developer-friendly, I mean anyone seeing this log message in their terminal can immediately tell the function scope of the variable being logged. The order of function scopes is parsed from the call stack provided by the NodeJS stack trace API. Hence the name, scope-logger.

  • CodeRabbit

    CodeRabbit: AI Code Reviews for Developers. Revolutionize your code reviews with AI. CodeRabbit offers PR summaries, code walkthroughs, 1-click suggestions, and AST-based analysis. Boost productivity and code quality across all major languages with each PR.

    CodeRabbit logo
  • debug

    A tiny JavaScript debugging utility modelled after Node.js core's debugging technique. Works in Node.js and web browsers

    Number of dependencies: one way to tell if a library is not too challenging to be used as study source is based on the production dependencies count. The fewer the better. For example, I chose debug because it only has 1 dependency (ms), while the rest of the code relies on core NodeJS modules - which is exactly what I was looking for - to learn how to build a library from scratch, not off the shelf libraries with many external deps, which in turn are based on more deps. There you go, dependency hell.

  • semver

    Semantic Versioning Specification

    Semantic Versioning: for every update (major, minor, or patch) made, increment the version number according to semantic versioning.

  • ms.js

    Tiny millisecond conversion utility

    Number of dependencies: one way to tell if a library is not too challenging to be used as study source is based on the production dependencies count. The fewer the better. For example, I chose debug because it only has 1 dependency (ms), while the rest of the code relies on core NodeJS modules - which is exactly what I was looking for - to learn how to build a library from scratch, not off the shelf libraries with many external deps, which in turn are based on more deps. There you go, dependency hell.

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts

  • Conditional logging

    1 project | dev.to | 10 Jan 2024
  • Has anyone figured out how to enable the millisecond diff feature in the debug package?

    1 project | /r/node | 16 Aug 2023
  • Help I have a JavaScript Lib that blows away competition but nobody knows of it

    2 projects | news.ycombinator.com | 14 Apr 2023
  • What is the DEBUG 🐛 environment variable in Node.js, and how to use it?

    1 project | dev.to | 4 Apr 2023
  • Automating console logs for dev but removing for prod?

    1 project | /r/webdev | 8 Mar 2023

Did you konow that JavaScript is
the 3rd most popular programming language
based on number of metions?