Why write a library?

• scope-logger

  1 0 8.6 JavaScript

  A NodeJs library that logs a variable and a sequence of scopes through which it's accessed

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.

• debug

  27 11,013 3.6 JavaScript

  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.

• SurveyJS

  surveyjs.io featured

  Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.

  

• semver

  727 7,044 0.6

  Semantic Versioning Specification

  

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

• ms.js

  8 4,987 3.7 TypeScript

  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.

Suggest a related project