PNPM Monorepo Nextjs SSR Not working

[rushi308]

Before opening, please confirm:

• I have checked to see if my question is addressed in the FAQ.
• I have searched for duplicate or closed issues.
• I have read the guide for submitting bug reports.
• I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
• I have removed any sensitive information from my code snippets and submission.

App Id

d23s4a8slavtvr

AWS Region

us-east-1

Amplify Hosting feature

Monorepo

Describe the bug

SSR is used with AWS Serverless Appsync GraphQL APIs in my pnpm Mono repository Nextjs app. I used AWS Amplify for hosting, however it returns a 500 error.

Expected behavior

It should work

Reproduction steps

1. Go to https://main.d23s4a8slavtvr.amplifyapp.com and it should work

Build Settings

version: 1
applications:
  - frontend:
      phases:
        preBuild:
          commands:
            - npm i -g pnpm
            - pnpm add project-schema --filter client --workspace
            - pnpm i
        build:
          commands:
            - npm run build
      artifacts:
        baseDirectory: .next
        files:
          - '**/*'
      cache:
        paths:
          - node_modules/**/*
    appRoot: apps/client

Log output

# Put your logs below this line

Additional information

No response

[ghost]

Hi @rushi308 👋🏽 we do not have monorepo support for SSR apps at this time but the team is aware of this and we are treating this as a priority.

[michrome]

Now available as a beta, Amplify Hosting has improved support for monorepo frameworks including npm/yarn/pnpm workspaces, Turborepo and Nx. If you'd like to try it out, please let me know your AWS Account ID number so we can flag you in. My email is [email protected].

[ghost]

We have recently launched support for Next.js applications using monorepos including the frameworks mentioned above. Please redeploy your applications to take advantage of this. Thank you!

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.