<https://pulumi-community.slack.com/archives/C84L4...
# general
n
https://pulumi-community.slack.com/archives/C84L4E3N1/p1570579979425900?thread_ts=1570568724.411700&amp;cid=C84L4E3N1 Anyone have advice on how they're structuring lambda projects that use AssetArchives instead of magic functions? It seems like the only reasonable way to do it is having multiple
package.json
files - one for each function. I'm imagining this will get really messy on deploy, as I would need to
npm install
in every folder on every deploy
t
Would all those
package.json
be the same? You could keep all functions in the same folder and have different entry points per each lambda.
n
I expect they would be slightly different, but with a fair amount of overlap
although maybe not. I was originally thinking I wouldn't want my global
node_modules
included, as that has all the pulumi crap... but a lambda-specific one wouldn't need any of that. I'll give it a try!
t
yeah, your lambda folder is just pure lambda