-
Notifications
You must be signed in to change notification settings - Fork 116
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
Build fails on amplify for node #3818
Comments
Hey @pankajsoni19, 👋 thanks for raising this! I'm going to transfer this over to our hosting repository for better assistance 🙂 |
Hi @pankajsoni19 👋 , thanks for reaching out. I observed that your Amplify app Today, if you create an Amplify app using our Classic SSR platform the Lambda@Edge functions for your app will use the Node 16 runtime and you should no longer see this error. That being said, we strongly recommend that you migrate your Next.js 11 apps to the Amplify Hosting compute managed SSR platform. For more information on how to migrate your classic app, refer to this documentation: https://docs.aws.amazon.com/amplify/latest/userguide/update-app-nextjs-version.html. |
This issue is now closed. Comments on closed issues are hard for our team to see. |
This issue has been automatically locked. |
Before opening, please confirm:
App Id
dnjuytvw4f7zx
Region
ap-southeast-1
Environment name
production
Figma File Version (if applicable)
No response
Amplify CLI Version
No response
If applicable, what version of Node.js are you using?
No response
What operating system are you using?
No response
Browser type?
No response
Describe the bug
Next Js build is failing with no changes done in code. Seems to be amplify internal error
build settings are >
amplify.yml
build image default,
nodeJS override > 16
error log
https://ap-southeast-1.console.aws.amazon.com/amplify/home?region=ap-southeast-1#/dnjuytvw4f7zx/master/29
Expected behavior
Build should compile as before about 4 months ago.
Reproduction steps
Project Identifier
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: