aws-amplify / aws-amplify/amplify-hosting
Creating Next.js app from AWS Amplify doesn't detect the framework
- Dominant language
- Dockerfile
- Stars
- 481
- Forks
- 123
- PR merge metrics
- No merged PRs in 30d
Description
### Environment information
```plain text
n/a
```
### Describe the bug
We have a Next.js v15 app deployed to vercel and it works well. Now we want to deploy the exactly same code to AWS Amplify instead. But when we tried to create new app, Amplify cannot detect the correct framework.
Below are screenshots taken while creating the app.



And package.json under packages/ops2-web-app is as below
```
{
"private": true,
"scripts": {
"build": "next build",
"dev": "next dev --turbo",
"start": "next start"
},
"dependencies": {
"@heroicons/react": "^2.1.4",
"@radix-ui/react-dropdown-menu": "^2.1.2",
"@radix-ui/react-label": "^2.1.0",
"@radix-ui/react-popover": "^1.1.2",
"@radix-ui/react-select": "^2.1.2",
"@radix-ui/react-slot": "^1.1.0",
"@radix-ui/react-tooltip": "^1.1.6",
"@tailwindcss/forms": "^0.5.7",
"@vercel/postgres": "^0.8.0",
"apexcharts": "^4.1.0",
"autoprefixer": "10.4.19",
"bcrypt": "^5.1.1",
"class-variance-authority": "^0.7.0",
"clsx": "^2.1.1",
"date-fns": "^3.6.0",
"lucide-react": "^0.460.0",
"next": "^15.0.0",
"next-auth": "5.0.0-beta.19",
"pg": "^8.13.1",
"postcss": "8.4.38",
"react": "^18.3.1",
"react-apexcharts": "^1.6.0",
"react-day-picker": "^8.10.1",
"react-dom": "^18.3.1",
"tailwind-merge": "^2.5.5",
"tailwindcss": "3.4.4",
"typescript": "5.5.2",
"use-debounce": "^10.0.4",
"zod": "^3.23.8"
},
"devDependencies": {
"@types/bcrypt": "^5.0.2",
"@types/node": "20.14.8",
"@types/pg": "^8.6.6",
"tailwindcss-animate": "^1.0.7"
}
}
```
Can anyone shred some light on what could be wrong here?
Thanks!
### Reproduction steps
n/a
Contributor guide
Research direction
Start with the package.json shown for packages/ops2-web-app and review the AWS Amplify app-creation flow represented by the attached screenshots. Reproduce the framework-selection behavior with this Next.js v15 application and compare the detected framework with the expected Next.js result; done means the app is recognized correctly during creation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, next.js
- Domain
- cloud, devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100