npm run build error Jest worker encountered 1 child process exceptions, exceeding retry limit

[arafat813]

Summary

PS E:\arafat2.0\blog> npm run build

[email protected] build
next build

▲ Next.js 14.1.0

• Environments: .env

Creating an optimized production build ...
Compiler server unexpectedly exited with code: 3221225725 and signal: null

Build error occurred
Error: Jest worker encountered 1 child process exceptions, exceeding retry limit
at ChildProcessWorker.initialize (E:\arafat2.0\blog\node_modules\next\dist\compiled\jest-worker\index.js:1:11580)
at ChildProcessWorker._onExit (E:\arafat2.0\blog\node_modules\next\dist\compiled\jest-worker\index.js:1:12545)
at ChildProcess.emit (node:events:529:35)
at ChildProcess._handle.onexit (node:internal/child_process:292:12) {
type: 'WorkerError'
}

Additional information

PS E:\arafat2.0\blog> npm run build

> fati_blog@0.1.0 build
> next build

   ▲ Next.js 14.1.0
   - Environments: .env

   Creating an optimized production build ...
Compiler server unexpectedly exited with code: 3221225725 and signal: null

> Build error occurred
Error: Jest worker encountered 1 child process exceptions, exceeding retry limit
    at ChildProcessWorker.initialize (E:\arafat2.0\blog\node_modules\next\dist\compiled\jest-worker\index.js:1:11580)
    at ChildProcessWorker._onExit (E:\arafat2.0\blog\node_modules\next\dist\compiled\jest-worker\index.js:1:12545)
    at ChildProcess.emit (node:events:529:35)
    at ChildProcess._handle.onexit (node:internal/child_process:292:12) {
  type: 'WorkerError'
}

Example

No response

[hasan-mohammad-bd]

Here are some potential solutions:

1. Run npm run clean and then try building again with npm run build.
2. Ensure that your file system is not corrupted and that you have sufficient disk space.
3. Try setting swc to false in your next.config.js file.

[arafat813]

Thank you for your response. I tried as you suggested, but it still doesn't work, and I also have enough disk space.

[SamOyeAH]

I am also encountering the same problem

[arafat813]

I have updated all packages using NPM update, and once this issue is resolved, you can also try it out

[SamOyeAH]

I have updated all my packages and I still receive the error unfortunately

[Ho3einWave]

did you manage to solve the issue?

[fernandesGabriel]

That is the same you have @Gustav-J

[sban2009]

any updates on this?

[arafat813]

I have updated all packages using NPM update, and once this issue is resolved, you can also try it out

[simplysantha]

i have same error please reply? anybody find solution?

[Hyodori04]

me too same error

[ElisefRaz17]

Me as well. My team had to update our next.js application to this version and I still haven't found a solution to it.

[alirizasahinn]

I'm having the same issue... Couldn't find literally no help on the internet for this topic, whenever you search always jest the testing framework pops up.

[netpoe]

I had the same issue.
Vercel sets the NodeJS version to the latest automatically (currently at 22.+). Set the version to what you use in your local machine and it should run the deployment correctly. In my case I was developing in NodeJS 20+ locally but Vercel had 22+.

If you set your NodeJS version in your machine to 22.+ and try to next dev your app, you should get the exact same errors as Vercel's.

[erichutabarat]

I had the same issue; I downgraded the Node version in the settings before redeploying, and it worked. more information here