Anthony Roach

I've tested the latest version of serverless-http with nextjs `nextConfig.experimental.outputStandalone` extensively and it works well. Also it looks like the nextjs `standalone` output type is no longer going to be...

I did end up running into one problem with API routes when there is a request body. Next.js has a built in body parser middleware that won't parse the body...

@johnforte You're welcome, I'm glad it saved you some time. I decided to use standalone just so the lambda zip was smaller. I tried using non-standalone and bundling with the...

Actually looks like `prune` can be set without a fork: ``` nextjs: { nextjsStaticAssetsProps: { prune: false, }, }, ``` And the dependency can also be added like so: ```...

I tested the above configuration and it eliminated the 403 errors on deploy. IMHO, the above settings should be the default because having your site break on deploy is not...

It's a race condition. If the static files get deployed before the server lambda, then the old files will have been deleted while the lambda is still serving HTML referencing...

Yeah, the lambda just renders the HTML from the server code inside the lambda itself, and the HTML contains URLs pointing at the static files that are then served out...

Browser caching certainly makes this error more likely to happen, but it can even happen with caching disabled if you hit the page right in the middle of the deploy....

You might not need this package at all. If you are just looking for aws-types types then the package is [@types/aws-lambda](https://www.npmjs.com/package/@types/aws-lambda). The package published by this repo is a CLI...

Please merge this. It is very confusing to have this package named `aws-lambda`.