Skip to content
This repository was archived by the owner on Feb 1, 2025. It is now read-only.
This repository was archived by the owner on Feb 1, 2025. It is now read-only.

API calls to _next/data fails with a 404 in standalone deployment with AWS Lambda #98

@js-sapphire

Description

@js-sapphire

I am building an SSR application with Next 13 with standalone output. No basepath. And I am using Page Router.
We have certain places where we are doing client side navigation which is triggering an API call ( _next/data/buildId/index.json ) but it fails with a 404. Now, these requests are being sent to the Lambda but they fail and that results in a page refresh.

My questions were:

  • In a standalone app, I can see we have code.zip and dependencies.zip, the two of which need to be deployed for Lambda. I dont see a file structure for /index.json. Is there a need for these files to exist in the directory ?
  • Is this a problem with Next 13 ?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions