1回答
- 新しい順
- 投票が多い順
- コメントが多い順
0
Hey,
Hope you're keeping well.
Amplify Console framework detection relies on scanning the selected monorepo root for build artifacts and config files like amplify.yml or amplify/ directories. In your first setup, because packages/backend is directly under the repo root, the detection logic is finding the Next.js app in packages/frontend first and inferring the framework from that. When you nest the workspace deeper, the scan starts from the specified folder and correctly identifies the Amplify backend.
To fix this without restructuring, explicitly set the build settings in the Amplify Console by editing the app’s build configuration and pointing it to the packages/backend path along with a custom `amplify.
Thanks and regards,
Taz
回答済み 1年前
