graceful-fs VS serverless-image-handler

async (config?: { /** * Overwrite the default ignored behavior */ customIgnored?: string[]; }) => { const projectRoot = getProjectRoot(); if (!projectRoot) return; // NB: fix to globally alter real fs in order to fix EMFile error that happens in TSMorph (see https://github.com/isaacs/node-graceful-fs) gracefulFs.gracefulify(realFs); console.log("Searching..."); const tsFunctions = await db.get("TsFunction"); const projectWatcherTsFunctions = tsFunctions.filter( (x) => x.explicitTypeName === "ProjectWatcher" ); const projectWatchers = projectWatcherTsFunctions .map((x) => x.name) .map((name) => sdk[name as keyof typeof sdk] as ProjectWatcher | undefined) .filter(notEmpty); log(`${projectWatchers.length} watchers gonna watch ${projectRoot}`, { type: "important", }); const startupWaitMs = 1000; setTimeout(() => { log( `There they are! \n\n${projectWatchers .map((projectWatcher) => { return `👁 👁 ${projectWatcher.name} ✅`; }) .join("\n")}`, { type: "success", } ); }, startupWaitMs); const startTimeAt = Date.now(); watch(projectRoot, { ignoreInitial: true, ignored: config?.customIgnored || [ "**/node_modules/**", "**/.next/**", "**/.expo/**", "**/build/**", "**/db/**", "**/.git/**", "**/.turbo/**", "**/generated/**", ], // alwaysStat: true, // not sure why I would need this, seems inefficient if I don't need it, I can simply run fs.stat }).on("all", (eventName, path, stats) => { if (Date.now() < startTimeAt + startupWaitMs) return; const relevantWatchers = projectWatchers.filter((watcher) => watcher.filter(eventName, path) ); oneByOne(relevantWatchers, async (projectWatcher) => { await projectWatcher(eventName, path); }); }); };

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.

graceful-fs https://www.npmjs.com/package/graceful-fs

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

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

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