waterloo-rocketry / minerva-old

Waterloo Rocketry's custom slackbot
3 stars 2 forks source link

Split up Lambda Function entry points into multiple files #74

Open QuantumManiac opened 1 year ago

QuantumManiac commented 1 year ago

Currently, the entry points for all of Minerva's lambda function are situated within the index.js file. This is not great, as it means that every single lambda function depends on all the code from all the function handlers and therefore any dead-code elimination from unneeded dependencies (e.g. tree-shaking) can't take place on a per-Lambda basis.

The best fix for this would be to move each Lambda entry function into its own file, and separate code accordingly.