sveltekit-adapter-lambda VS update-lambda-edge

I have a sveltekit app, it talks to an AWS REST backend so I would prefer to host it on AWS. I am exploring different ways of doing this. I am thinking of deploying to either Beanstalk or to Lambda or Serverless. I have played with Pulumi which looks pretty nice, but I could not get AWS to read the artefact zip file correctly after following all the instructions. Could not find package.json but it was there. Yes I zipped the files not the folder. I also tried sveltekit-adapter-lambda which uses serverless, but I hit problems with none of the static assets being accessible. Sites up, but 404s on all the js and css. They are there on the S3 bucket and being served up ok via the bucker URL but not coming through the lambda function.

Please take a look at this https://github.com/yarbsemaj/sveltekit-adapter-lambda

In my organisation for the deployment of the latest version of code running on lambda@edge, we have written a script which uses update-lambda-edge npm package to deploy the latest code of lambda and also attach the latest version of it to different CacheBehaviours of CDN. The CLI utility allows only a single CacheBehaviour in single command while attaching the lambda to triggers so for multiple paths we run the command in the loop, till now things were fine, but since yesterday it started failing frequently, upon debugging I found that it was failing on the 5th entry of CacheBehaviour, if we're trying to update 4 behaviours it works fine.