Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue: Deploying Turborepo Monorepo with Next.js 15 to AWS Amplify #3989

Open
3 tasks done
ahtisham-gsoftconsulting opened this issue Jan 21, 2025 · 2 comments
Open
3 tasks done
Labels
feature-request New feature or request

Comments

@ahtisham-gsoftconsulting

Before opening, please confirm:

Amplify Hosting feature

Monorepo, Build settings, Deployments, Frontend builds

Is your feature request related to a problem? Please describe:

I’m currently working on deploying a Turborepo-based monorepo to AWS Amplify, and I’m running into some issues. My setup includes Next.js 15 in the monorepo structure, and the Amplify build successful generated and deployed but when i click on link fails with 500
error Here are the key issues I’m facing: logs list in cloud watch node:internal/modules/cjs/loader:1228 2025-01-20T10:10:05.164Z Error: Cannot find module ‘next/dist/server/lib/start-server.js’ here is build settings file node version 22 version: 1 applications:

version: 1
applications:

frontend:
phases:
preBuild:
commands:
nvm use 22
yarn install
build:
commands:
yarn run build --filter=omnipulse
artifacts:
baseDirectory: apps/appname/.next
files:
'/'
cache:
paths:
node_modules//

.next/cache/
/*
apps/appname/node_modules//*
apps/appname/.next/cache/
/*

Image

buildPath: /
appRoot: apps/appname

Describe how you'd like this feature to work

when i click on link it should be open website

@ahtisham-gsoftconsulting ahtisham-gsoftconsulting added the feature-request New feature or request label Jan 21, 2025
Copy link

This has been identified as a feature request. If this feature is important to you, we strongly encourage you to give a 👍 reaction on the request. This helps us prioritize new features most important to you. Thank you!

@iamaralinvestplay
Copy link

I had the same issue. I realized that it occurs when the assetPrefix attribute in the next.config.js file is setted up.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants