Stuck on Creating an optimized production build forever when development server is running

[YassinEldeeb]

Verify canary release

• I verified that the issue exists in Next.js canary release

Provide environment information

Operating System:
Platform: win32
Arch: x64
Version: Windows 10 Pro
Binaries:
Node: 16.13.0
npm: N/A
Yarn: N/A
pnpm: 6.24.0-1
Relevant packages:
next: 12.1.4
react: 17.0.2
react-dom: 17.0.2

What browser are you using? (if relevant)

No response

How are you deploying your application? (if relevant)

No response

Describe the Bug

I had my development server running in the background without me remembering and I wanted to build my app using next build, that's what I've got:

$ yarn next build
yarn run v1.22.17
$ C:\development\activity-builder\node_modules\.bin\next build
info  - Loaded env from C:\development\activity-builder\.env
info  - Checking validity of types  
warn  - The Next.js plugin was not detected in your ESLint configuration. See https://nextjs.org/docs/basic-features/eslint#migrating-existing-config

./src/components/Activities/ActivityQuestions/DynamicQuestionTypes/MultipleChoice.tsx  
68:40  Warning: Forbidden non-null assertion.  @typescript-eslint/no-non-null-assertion
69:22  Warning: Forbidden non-null assertion.  @typescript-eslint/no-non-null-assertion

./src/components/Activities/ActivityQuestions/Question.tsx
102:13  Warning: Unexpected console statement.  no-console

info  - Need to disable some ESLint rules? Learn more here: https://nextjs.org/docs/basic-features/eslint#disabling-rules
info  - Creating an optimized production build  

And I was stuck for 30 minutes on info - Creating an optimized production build without any indication of anything being wrong, I noticed that the development server was running, after I've shut it down and ran next build again It compiled successfully.

Expected Behavior

• Run next build to compile the app for production even when I'm running the development server.

  OR

• Notify me that the development server is running and needs to be shut down before running next build, that's in case running next build when next is running isn't possible.

Link to reproduction

https://github.com/YassinEldeeb/Next.js-starter

To Reproduce

1. Run next for the development server.
2. Then run next build while the development server is running.

Note: It's not specific to the repository linked above.

[pulkitvyas08]

Facing the same issue

[huanlirui]

i have same issue !!

[huanlirui]

Execute the steps of “ creating an optimized production build ” on the Linux server

node v14.17.0

[benzavision]

same issue

[MarcusHSmith]

Same issue for us

[UmerEdava]

The same issue still exists.... any remedies. In my case, it was hours I stuck at this "creating an optimized production build". And also I didn't run the development server in the background.

[boiboif]

same issue!

[iamharshad]

Same issue for React.js project as well even when development server is not running on

[Dariocoding]

I have the same issue!!!

[zahydo]

Same Issue. In development it worked, but when I try to create the Docker image it stuck

[zahydo]

Same Issue. In development it worked, but when I try to create the Docker image it stuck

I solved with the next steps:

1. Upgrading Next to v12.2.5.
2. Removing local folders: .next, node_modules
3. Installing dependencies again: yarn install
4. Adding this to next-config.js: output: 'standalone'
5. Adding the next paths to the .dockerignore:
   Dockerfile
   .dockerignore
   node_modules
   npm-debug.log
   README.md
   .next
   docker
   .git
6. Creating the image again: docker build ...

[alexrintt]

Stuck on Creating an optimized production build forever when development server is running.

Same issue but I wasn't aware that this was happening due the open dev webserver.

So the solution for me is on your title: close the development server, then run next build and next export (If you intend to deploy statically).

[XahidEx]

I am still facing the same issue. Using the latest NextJs 12.3.2-canary.34 facing this issue since I'm trying 12.3.2-carany.+

[ruvaz]

You can't have both dev and build at the same time.

I solved it very quickly when I realized that there were several nodejs processes open when there should only be 1, and killing all the nodejs processes that were running in the background solved it for me.

It can also happen that a build started to fail and got stuck in the background so you should kill all the nodejs you see running in the task manager. I am using Nextjs 13

[celenac]

Killing the nodejs background processes in my Task Manager worked. Ending the process in the terminal and/or closing the terminal wasn't enough. Thanks!

[XahidEx]

Mine was also solved. I faced this issue because a dependency wasn't comfortable with the latest nextjs. 🙃
Vercel didn't show the error anyway. It was just stuck. 😅

[percy507]

I solved it by fixed eslint version.

    "eslint": "8.34.0",
    "eslint-config-next": "13.2.1",

[MattiaPeiretti]

When I run npm run build inside a docker container. It never builds and is for me stuck on "Creating an optimized production build ..." as well
I followed Vercel's guide on dockerisation and their freshly cloned example also hangs forever. If you check the picture above, mine is still hanging after running for 6200+ seconds (1h+).
The problem is very likely not:

• Version, everything is up to date as of 06.10.2023
• RAM, docker has 20 GB of RAM it can use

What I noticed about the docker build command (both tested for fresh Vercel example as well as my own dockerised project(nextjs project with app dir)), is that on macOS Sonoma, it hangs forever. HOWEVER, if I pull the same exact files and build the project on my Linux PopOs machine, it builds just fine.
So for me, it could be a configuration issue or some Docker-Sonoma issue.
Does anyone else see themselves in this issue as well?

the same. have you solved this problem? i almost tried everything i could do. delete the cache, update dependency to latest version, but it is still stucking on the step.
And i tried to build this project in local, it completed very soon. But stuck on the step when i build it in docker.

i fixed that by using OrbStack to use 'docker build' command. The problem seems to be caused by Docker Desktop.

This!!!!!
Docker Desktop is the problem. For anyone trying to run next build in a container, via Docker Desktop on Mac M1/M2.
My builds would often fail, and sporadically work. When it worked, it could take 30 minutes to an hours.
I switched to OrbStack and the build worked flawlessly, in about 2 minutes.

That was the solution for me as well. I've switched to OrbStack and it worked seamlessly.

Great to hear! I will try this.
For now, I have either used GitHub actions which run Ubuntu, or my own VPS. I'm really looking forward to trying OrbStack!

[jpbalarini]

When I run npm run build inside a docker container. It never builds and is for me stuck on "Creating an optimized production build ..." as well

I followed Vercel's guide on dockerisation and their freshly cloned example also hangs forever. If you check the picture above, mine is still hanging after running for 6200+ seconds (1h+).

The problem is very likely not:

• Version, everything is up to date as of 06.10.2023
• RAM, docker has 20 GB of RAM it can use

What I noticed about the docker build command (both tested for fresh Vercel example as well as my own dockerised project(nextjs project with app dir)), is that on macOS Sonoma, it hangs forever. HOWEVER, if I pull the same exact files and build the project on my Linux PopOs machine, it builds just fine.

So for me, it could be a configuration issue or some Docker-Sonoma issue.

Does anyone else see themselves in this issue as well?

In my case, I suspected that it was some virtualization issue, and I was right. Once I disabled Rosetta for x86/amd64 emulation in my Docker desktop config I was able to build my image successfully!

[MattiaPeiretti]

When I run npm run build inside a docker container. It never builds and is for me stuck on "Creating an optimized production build ..." as well
I followed Vercel's guide on dockerisation and their freshly cloned example also hangs forever. If you check the picture above, mine is still hanging after running for 6200+ seconds (1h+).
The problem is very likely not:

• Version, everything is up to date as of 06.10.2023
• RAM, docker has 20 GB of RAM it can use

What I noticed about the docker build command (both tested for fresh Vercel example as well as my own dockerised project(nextjs project with app dir)), is that on macOS Sonoma, it hangs forever. HOWEVER, if I pull the same exact files and build the project on my Linux PopOs machine, it builds just fine.
So for me, it could be a configuration issue or some Docker-Sonoma issue.
Does anyone else see themselves in this issue as well?

the same. have you solved this problem? i almost tried everything i could do. delete the cache, update dependency to latest version, but it is still stucking on the step.
And i tried to build this project in local, it completed very soon. But stuck on the step when i build it in docker.

i fixed that by using OrbStack to use 'docker build' command. The problem seems to be caused by Docker Desktop.

This!!!!!
Docker Desktop is the problem. For anyone trying to run next build in a container, via Docker Desktop on Mac M1/M2.
My builds would often fail, and sporadically work. When it worked, it could take 30 minutes to an hours.
I switched to OrbStack and the build worked flawlessly, in about 2 minutes.

That was the solution for me as well. I've switched to OrbStack and it worked seamlessly.

Great to hear! I will try this. For now, I have either used GitHub actions which run Ubuntu, or my own VPS. I'm really looking forward to trying OrbStack!

I tried OrbStack, it gave a nice performance boost, but it did not solve the issue.

[auxibee]

I solved this issue by using CMD in the final build step instead of RUN

RUN npm run build

CMD [ "npm", "run", "start" ]

[theneroweb]

i just upgraded nodejs to the latest version and worked like a charm
previous version 17.9.1 to 20.10.0

[parlato-vooma]

I had the same issue and I found out the cause by adding this to my next.config.js - suggested by @andersekdahl

process.on('unhandledRejection', error => {
	console.log('unhandledRejection', error);
});

Extremely helpful - we'd removed a dependency with a transitive dependency we relied on implicitly. We were only able to determine this with the above process log.

[HajAbdolblack]

I actually had this problem and I managed to fix it by upgrading my Linux machine memory

[samcx]

Hi everyone!

I will be moving this to Discussions, as this issue can arise from a variety of different ways, and different solutions to resolve those.

We still encourage folks to file bugs outside of this thread detailing the exact issue, with a and details on how to consistently reproduce the issue!

Happy 2024!

[punjasin]

i also have this issue it work fine on my mac m1 pro 32gb

but not on starter packakge on vps service like (5 usd digital ocean,ligstsale ,linode) it will take forever
my solution is make some swap memeory 4-8gb is enough to make it pass the build step

[HelmerBarcos]

Same here while building on Self managed GitLab (Kubernetes cluster + kubernetes runner)

[renny-ren]

Same here, I've tried:

• stop dev server
• remove .next folder
• remove node_modules
• remove yarn.lock and run yarn install again
• upgraded node to 20.10.0
• upgraded next.js to 14.1.0

None of them worked, it just stuck on Creating an optimized production build ... forever, this issue drives me crazy!

[ManInTheWind]

Same! so what the heck going on when npm run build inside docker

[fedu]

+1

[rayansindi1]

In my case, it works fine when I run build on my local machine but it gets stuck forever when building docker image.

I was using "oven/bun" as my base docker image and I suspected that the issue is from bun's image.

So, I switched to "node:20.11.1-slim" base docker image and I ran "npm install -g bun" in my Dockerfile to install bun and it worked like a charm!

I hope this helps someone