Echo JS 0.11.0

Only criticism is this is using a blocking sync interface... don't do this in a service app that receives requests from externally.  You could do largely the same with async, you'd have to replace the array methods with for loops though.

On a very large/deep directory structure (root on a unix system), you'll likely get a stack overflow exception.

MIT License, Github Url: https://www.pixijs.com/

This caching is per instance... the main issue with caching in memory, especially in something like a cloud function is functions aren't really long-lived.  It's different if you're running few instances of a persistent service, quite another if you're in a FaaS.

Depending on the round-trip-time to the query service, it may be better to not cache.  If it's expensive, then it's likely best to cache in an indexed key/value store such as redis or other local/near DB.

Also worth looking at...

https://github.com/GoogleChromeLabs/squoosh

https://github.com/brunobar79/J-I-C

Changed link to point to actual site article.  The component itself seems to be a commercial component.  Would be nice to have more insight into how the size reduction was accomplished though.  As it is, it's kind of a fluffy release article.

Nice module... one suggestion to anyone using this, make sure your minutes window supports your retry timeout for the outbound mail service/server.  Many hosts will do a greylist option on inbound emails, relying on the retry for SMTP servers to reduce inbound spam.  If you run your own SMTP server, set the first retry to 1 minute (default is usually 15 minutes).  This way a greylist receiving server will get the message within the window.

If you're using a service that you don't control, you should set the window to 30-60 minutes.  I would suggest looking into a delivery service like mailgun or sendgrid for these types of things, you'll see much better delivery rates for the big ISPs and mail providers.

Off topic, but good information to understand.

Been waiting for optional chaining for some while now.  Really want the linter in VS Code to support it already, been using it via Babel, but the UI linting errors visible are a little annoying.

It's worth noting that *MOST* of these "consent" implementations are flat out *wrong* … what you are supposed to do, is *NOT* include 3rd party tracking scripts that use cookies until *AFTER* you've gotten consent. In practice, you aren't getting consent as you've already tracked the user in a meaningful way by including your analytics, ads etc.

When using this, you should only put in tracking/analytics/ads after the user hits the consent option.