feature: option to download chrome binary on cold start rather than bundling in function zip
Currently, the Serverless plugin bundles the headless chrome binary in the artifacts that's uploaded during Lambda function deployment. This is great for function invocation because we don't have to waste time downloading the binary on a Lambda function's cold start, saving time. However, it means uploading a zip file that's around 48 MB which can be painfully slow during development. It also means there's little room left for other dependencies. Therefore, this feature enhancement would make it an option to download on invocation, rather than on zip bundling.
This feature would be implemented in the @serverless-chrome/lambda package, and exposed in the serverless plugin (with the appropriate artefact optimisations—e.g don't include the headless_shell binary.)
While the article is not entirely accurate, this feature is inspired by this blog post.
Any update on this? Need any help?