Side note: This also means there is no difference between `devDependencies` and `dependencies`. Webpack makes sure each deployed service only has what is needed in the bundle.
-
-
Show this threadThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
I think this is the architecture that
@hanamirb is shooting for too. -
woah! I had not seen this. Will dig in. If we could just get one of the cloud providers to support ruby!
End of conversation
New conversation -
-
-
This is exactly what we're looking at doing at work.

-
It is why I made shep do it by default. If you are deploying to cloud fns it is almost a requirement. Cold starts are real, code package size matters, and require is slow. You're throwing a lot of perf away if you don't bundle.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
In nodejs world, I bet we'll see more people code splitting their backends. Develop in a monorepo and deploy to code split + webpacked microservices or cloud functions.