API calls to _next/data fails with a 404 in standalone deployment with AWS Lambda about nextjs-lambda HOT 5 OPEN

That was a typo. The request is expected. Origin of request is the client. When there is a client side navigation within the app on the same route ( but on a different query string parameter ), client makes a request to getServerSideProps in the form of /_next/data/buildId/index.json. However, it seems Lambda is not able to figure out what to make of it.

Not a typo. Happened because I used carets

from nextjs-lambda.

@js-sapphire I tried replicating without much luck :/ could you try to share repo steps?
I will try to support you, however, please consider EOL (#97) for this package.

from nextjs-lambda.

Hey!
_next/data are basically API route I believe. It's handled by Next's server.

'_next/data/*': {
     ...defaultOptions,
     origin: serverOrigin,
},

What seems weird is that doubled // in your path _next/data//index.json. I would imagine that causing and issue probably. Question is, why is it doubled 🤔 Could you investigate the origin of this request (I would expect getServerSideProps making it).

from nextjs-lambda.

I can spin up an example and share repo if that helps. I couldn't find much info on Next SSR Standalone + AWS Lambda but for your package's github. Let me know if that'd help in your investigation ( if you have time for this ofcourse )

from nextjs-lambda.

Thanks @sladg
Will share ASAP.

from nextjs-lambda.