You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
NEW_APP
AWS Region
us-east-1
Amplify Hosting feature
Build settings
Frontend framework
JavaScript
Next.js version
N/A
Next.js router
N/A
Describe the bug
Front End BUILD FAILED, NON ZERO EXIT CODE DETECTED. Tried to update build settings to choose proper artifact folder. Decided to create folder during prebuild and move files in.
Expected behavior
Build was supposed to succeed.
Reproduction steps
Modify build settings artifact field to build root directory.
Hi @mcdeagles 👋 , thanks for reaching out. The default build directory for your app will vary based on your app framework. For example, if you are building a react app via CRA it will generate a build directory for your artifacts when you do a production build via npm run build. If you want to use a custom folder instead of build for the output, you can achieve this via either of the methods:
This issue is now closed. Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.
Before opening, please confirm:
App Id
NEW_APP
AWS Region
us-east-1
Amplify Hosting feature
Build settings
Frontend framework
JavaScript
Next.js version
N/A
Next.js router
N/A
Describe the bug
Front End BUILD FAILED, NON ZERO EXIT CODE DETECTED. Tried to update build settings to choose proper artifact folder. Decided to create folder during prebuild and move files in.
Expected behavior
Build was supposed to succeed.
Reproduction steps
Build Settings
Log output
Additional information
Question: How do you find the root build directory to use in the artifact build setting. I created my own build folder instead.
The text was updated successfully, but these errors were encountered: