pify
serverless-image-handler
pify | serverless-image-handler | |
---|---|---|
2 | 4 | |
1,497 | 1,260 | |
- | 0.5% | |
0.0 | 4.2 | |
over 1 year ago | about 1 month ago | |
JavaScript | TypeScript | |
MIT License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
pify
-
My theory on why so many people are bad at coding.
What's probably got your shorts in a knot is the contents of the node_modules directory. That directory is a cache for mode.js modules so the tutorial can function standalone without having to install anything else. Treat it as you would object code. I pulled a half-dozen of those modules at random and went to their repositories. Every one of them had unit tests: block-stream, graceful-fs, lowercase-keys, minimist, pify and safe-buffer. Nobody sane ships unit tests with their executables.
-
what's your hidden gem package?
Not sure it’s hidden but I really like pify to promisify things, really cleaned up my multer calls.
serverless-image-handler
-
How to perform on fly image resize from CloudFront if it does not exist in the S3 origin ?
AWS Suggests this if you want to do regular lambda + CF cache and they say it is production quality: https://github.com/aws-solutions/serverless-image-handler
- My theory on why so many people are bad at coding.
-
AWS for Photos
I use imgix to resize images on the fly, which I recommend, but given the large amount of images you have it may not be cost effective. You could look into running your own: https://github.com/aws-solutions/serverless-image-handler
-
The Hacker Who Archived Parler Explains How She Did It (and What Comes Next)
It looks like there’s a ‘standard service’ for video media: https://aws.amazon.com/elastictranscoder/ but actually for jpg you might need to do something a bit more bespoke. You could deploy a ‘serverless’ lambda function to do this conversion and write the S3 urls to a database after: https://github.com/awslabs/serverless-image-handler. Looks like it uses SharpJS: https://sharp.pixelplumbing.com/. In the past I’ve used ImageMagick on compute instances: https://imagemagick.org/script/index.php
What are some alternatives?
Bluebird - :bird: :zap: Bluebird is a full featured promise library with unmatched performance.
base65536 - Unicode's answer to Base64
pinkie-promise - Promise ponyfill with pinkie
parler-grab - Archiving Parler.
promise-memoize - Memoize promise-returning functions. Includes cache expire and prefetch.
lowercase-keys - Lowercase the keys of an object
valvelet - Limit the execution rate of a function
image-optimization - Simple, performant and cost efficient solution for optimizing images using Amazon CloudFront, Amazon S3 and AWS Lambda
p-map - Map over promises concurrently
lambda-edge-resizing-images-custom-origin - Sample code for resizing Images with Lambda@Edge using the Custom Origin. You can deploy using AWS CDK.
rfpify - [DEPRECATED] Promisify a result-first callback function.
graceful-fs - fs with incremental backoff on EMFILE