aws-amplify / aws-amplify/amplify-hosting

Auto-detected frameworks detects Next.js with no Next.js app in monorepo

Open
#4,028 6 comments 0 reactions 0 assignees View on GitHub
bug console
Dominant language
Dockerfile
Stars
481
Forks
123
PR merge metrics
No merged PRs in 30d

Description

### Environment information

```plain text
npm error could not determine executable to run
npm error A complete log of this run can be found in: /home/ty/.npm/_logs/2024-05-30T13_26_34_967Z-debug-0.log
```

### Description

I do not have a Next.js app in my monorepo, Amplify Gen2 "auto-detects" Next.js whenever I select the app I want to deploy.

![image](https://github.com/aws-amplify/amplify-hosting/assets/6652493/02b42d45-5c53-46b8-99b3-02e5b8d6f699)

Contributor guide

Open the contributing guide

Research direction

No source files, tests, or entry points are identified in the issue. First reproduce auto-detection with a monorepo that has no Next.js app and inspect the detection flow; done means Amplify no longer selects Next.js for that repository while still detecting an actual Next.js app.

Written by the indexing model from the issue text.

Assessment

Tech stack
next.js
Domain
cloud, devops
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.