Agreed. We got around this by hacking the single use CVS/Rite Aid cameras according to the below guide. Dropping one of these in the water or on some rocks didn't feel quite so devastating.
First thought (to the article title "Why we stopped building fatjars") was that the build person had "graduated" and took their newly "acquired superpowers elsewhere" [0]
Joking aside, fantastic idea =)
Have you received a cease and desist from SlimFast yet for violating their trademark?
They've already increased it from the originally published concurrent requests per function limit (originally 50, now 100) [1]
We'd like the "Total size of all the deployment packages that can be uploaded per account" increased. Since you have to "require in" (as you put it) all your dependencies with each published function it's plausible to hit that limit pretty quick.
The average node module is 1.6MB [2]. If your functions have 3 dependencies, you're near 5MB. That limits you to ~300 functions. That initially seems like a lot until you realize you may have to start breaking up complex logic into multiple functions to hit time limits. You also might need to maintain multiple versions for backwards compatibility (think v1 endpoints). And if you use Java 8, you're just screwed. That size limit can be hit quick.