@tommedema thanks for your reply. we will do our part to raise awareness on serverless + monorepo.
as a developer, if you are using serverless, you also are probably maintaining more code in your codebase. therefore it follows that a serverless user is very likely to benefit from a monorepo solution.
btw, the way we resolved our issue was by removing a bloated package from the dependencies.
we also took a deep look into how serverless packages and zips files. the pattern matching algorithm in our usecase was mapping to about 200,000 files. processing all of those guys takes a reaaaaallly long time. so i actually like your approach to highjack the artifact generation, as the current algorithm is a bit inefficient. it definitely gets the job done for small code bases, but cant keep up on the bigger ones.
we had to rewrite a big package we’ve been using all over our codebase, in order to shrink the size, and the number of files the algorithm needs to process.
thanks for your help, and your initiative in creating this example codebase. it has helped us quite a bit, and i’m sure lots of other people will find it helpful too!