Next.js v15 Template Not Working with Amplify Gen 2 + Node.js 18 (EOL)

[raihanbrillmark]

---

"Next.js v15 Template Not Working with Amplify Gen 2 + Node.js 18 (EOL)"
Labels: [bug, framework:nextjs, amplify-gen2]

🐛 Bug Report

Summary

The default template for Next.js v15 is currently not working with Amplify Gen 2, and the environment appears to be using Node.js 18, which is now End-of-Life (EOL).

This causes build failures and incompatibility issues, particularly with modern dependencies that require newer Node.js versions (e.g., 20+).

---

Expected Behavior

Amplify Gen 2 should:

• Support the latest stable version of Next.js (v15)
• Use a non-EOL Node.js runtime (preferably Node.js 20 or higher)
• Offer an up-to-date template for Next.js that reflects current best practices

---

Current Behavior

• Amplify Gen 2 fails to build or deploy apps using Next.js v15
• npm ci or npm install errors due to unsupported or outdated dependencies
• Lockfile errors (e.g., missing @smithy/* packages)
• Node.js 18 EOL leads to security and compatibility concerns

---

Steps to Reproduce

1. Create a new Amplify Gen 2 app
2. Use the default Next.js v15 template (or manually configure a project with Next.js v15)
3. Deploy the app using amplify publish or through the Amplify Console
4. Observe build failures and warnings related to Node.js runtime and npm dependency resolution

---

Suggested Fix

• Update Amplify Gen 2’s default Node.js runtime to Node.js 20+
• Provide an official Amplify Next.js v15 template compatible with the new runtime
• Document supported versions of Next.js and Node.js more clearly in the Amplify docs

---

Environment

• Framework: Next.js v15
• Amplify: Gen 2
• Node.js: 18 (EOL as of April 2025)
• Package manager: npm
• Hosting: Amplify Console / CI/CD

---

Additional Context

According to the official Node.js release schedule, Node.js 18 has reached end of life in April 2025, making its use problematic for new and existing apps.

---

Please let us know if there’s an expected timeline for Next.js v15 + Node.js 20 support in Amplify Gen 2.

Thanks for your continued work on Amplify!

[raihanbrillmark]

Console logs prints

2025-07-29T18:08:38.537Z [INFO]: # Build environment configured with Standard build compute type: 8GiB Memory, 4vCPUs, 128GB Disk Space

1

2025-07-29T18:08:39.413Z [INFO]: # Cloning repository: git@github.com:raihanbrillmark/inteliconvert-chatbot.git

2

2025-07-29T18:08:40.991Z [INFO]: 

3

2025-07-29T18:08:40.991Z [INFO]: Cloning into 'inteliconvert-chatbot'...

4

2025-07-29T18:08:40.991Z [INFO]: # Switching to commit: 2de2faa1bd02002e7c69de561f51593adeaf4cb4

5

2025-07-29T18:08:41.008Z [INFO]: Note: switching to '2de2faa1bd02002e7c69de561f51593adeaf4cb4'.

6

                                 You are in 'detached HEAD' state. You can look around, make experimental

7

                                 changes and commit them, and you can discard any commits you make in this

8

                                 state without impacting any branches by switching back to a branch.

9

                                 If you want to create a new branch to retain commits you create, you may

10

                                 do so (now or later) by using -c with the switch command. Example:

11

                                 git switch -c <new-branch-name>

12

                                 Or undo this operation with:

13

                                 git switch -

14

                                 Turn off this advice by setting config variable advice.detachedHead to false

15

                                 HEAD is now at 2de2faa feat(setup): project

16

2025-07-29T18:08:41.108Z [INFO]: Successfully cleaned up Git credentials

17

2025-07-29T18:08:41.109Z [INFO]: # Checking for Git submodules at: /codebuild/output/src3902977541/src/inteliconvert-chatbot/.gitmodules

18

2025-07-29T18:08:41.118Z [INFO]: # Retrieving environment cache...

19

2025-07-29T18:08:41.175Z [WARNING]: ! Unable to write cache: {"code":"ERR_BAD_REQUEST","message":"Request failed with status code 404"})}

20

2025-07-29T18:08:41.175Z [INFO]: ---- Setting Up SSM Secrets ----

21

2025-07-29T18:08:41.175Z [INFO]: SSM params {"Path":"/amplify/dj95vbtzn3c6a/main/","WithDecryption":true}

22

2025-07-29T18:08:42.160Z [INFO]: # No package override configuration found.

23

2025-07-29T18:08:42.270Z [INFO]: # Retrieving cache...

24

2025-07-29T18:08:42.315Z [INFO]: # Retrieved cache

25

2025-07-29T18:08:46.746Z [INFO]: ## Starting Backend Build

26

                                 # Starting phase: build

27

                                 # Executing command: npm ci --cache .npm --prefer-offline

28

2025-07-29T18:09:06.132Z [WARNING]: npm warn ERESOLVE overriding peer dependency

29

2025-07-29T18:09:06.140Z [WARNING]: npm warn While resolving: @xstate/react@3.2.2

30

                                    npm warn Found: react@19.1.0

31

                                    npm warn node_modules/react

32

                                    npm warn   react@"19.1.0" from the root project

33

                                    npm warn   45 more (@aws-amplify/ui-react, @aws-amplify/ui-react-core, ...)

34

                                    npm warn

35

                                    npm warn Could not resolve dependency:

36

                                    npm warn peer react@"^16.8.0 || ^17.0.0 || ^18.0.0" from @xstate/react@3.2.2

37

                                    npm warn node_modules/@aws-amplify/ui-react-core/node_modules/@xstate/react

38

                                    npm warn   @xstate/react@"^3.2.2" from @aws-amplify/ui-react-core@3.4.3

[raihanbrillmark]

This starter template has not yet addressed important Next.js security concerns. Please prioritize resolving these issues as soon as possible.

Ref: https://vercel.com/blog/postmortem-on-next-js-middleware-bypass