ms.js VS pretty-ms

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.

8.ms

For recurring habits I just store an ms string, when I tick something off it adds that time for the next time it's due. Easy peasy.

Next.js Redux Toolkit Framer Motion Tailwind Radix UI Radix colors react-use clsx lodash ms

I've been fighting this in many places, but of course there are fools out there who actually defend this practice rather than be indifferent to it at worst. Fixing it in those two places would actually fix about 70–80% of all such instances, since many websites just depend on those libraries. Feel free to upvote them, respectively.

The final and most important function of our Lambda, the loadParameters function accepts a single value named expiryTime that is by default set to 1 hour and can be overridden. I have used the ms library to set human readable time periods which will be automatically converted to milliseconds.

Recently, some of the npm packages I was using together with Serverless Framework had upgraded to 'pure ESM'. This meant that they no longer supported the older CommonJS require syntax and I needed to figure out how get Webpack to bundle eveything up nicely again to deploy as a CommonJS AWS lambda.