Next.js Discord

Discord Forum

Stuck on npm run build

Answered
Mulo posted this in #help-forum
Open in Discord
MuloOP
running v Next.js v13.0.3
did try to uninstall all node_modules and pkg.lock.json
reinstalled all, still same issue

ubuntu@vps-10ed:~$ ps aux | grep node
ubuntu     16377  0.3  2.9 43994264 232572 pts/3 Dl   11:44   0:19 node /home/ubuntu/appbot/node_modules/.bin/next build
ubuntu     17137  0.4  5.2 44214232 417736 pts/1 Dl   11:52   0:22 node /home/ubuntu/appbot/node_modules/.bin/next build
ubuntu     24439 14.9  8.8 55296924 702020 pts/5 Dl+  13:13   0:53 node /home/ubuntu/appbot/node_modules/.bin/next build
ubuntu     24577  0.1  0.0      0     0 pts/5    Z+   13:14   0:00 [node] <defunct>
ubuntu     24579  0.2  0.0      0     0 pts/5    Z+   13:14   0:00 [node] <defunct>
ubuntu     24595  0.1  0.0      0     0 pts/5    Z+   13:14   0:00 [node] <defunct>
ubuntu     24721  0.0  0.0   7076  2048 pts/2    S+   13:19   0:00 grep --color=auto node

trying sudo kill those processes does nothing
Answered by Mulo
## For those that will see this issue in the future:
I fixed it by adding outputFileTracing: false, in the next.config file.
It is said that this solution is valid if
- You're not deploying to Vercel or other serverless platforms.
- You're running the app via next start on your own VPS or Node.js environment.
- You're not using serverless output or custom edge functions.
View full answer

6 Replies

MuloOP
I have 4vcores, 8GB ram
system is idle but the cmd prompt still show building...
ubuntu@vps-10ed1d:$ ps aux | grep 'next build'
ubuntu     16377  0.2  2.9 43994264 232572 pts/3 Dl   11:44   0:19 node /home/ubuntu/appbot/node_modules/.bin/next build
ubuntu     17137  0.3  5.2 44214232 417736 ?     Dl   11:52   0:22 node /home/ubuntu/appbot/node_modules/.bin/next build
ubuntu     24439  3.8  8.8 55296924 702020 ?     Dl   13:13   0:53 node /home/ubuntu/appbot/node_modules/.bin/next build
ubuntu     24955  2.6  3.3 54846964 262716 pts/6 Dl   13:23   0:22 node /home/ubuntu/appbot/node_modules/.bin/next build
ubuntu     25425  0.0  0.0   7080  2048 pts/7    S+   13:37   0:00 grep --color=auto next build
MuloOP
## For those that will see this issue in the future:
I fixed it by adding outputFileTracing: false, in the next.config file.
It is said that this solution is valid if
- You're not deploying to Vercel or other serverless platforms.
- You're running the app via next start on your own VPS or Node.js environment.
- You're not using serverless output or custom edge functions.
Answer