Next JS : Error: EPERM: operation not permitted, open

Question

I am trying to build the next Js app production files to deploy it on cPanel, when I execute npm run dev the app is working just fine but as I start to build a production file with the help of this video(https://youtu.be/1ykSXau838c) and executes npm run build it gives me an error in the terminal as given below:

PS C:\Users\hp\Desktop\reactJs-project\NextJs\test-app> npm run build

> [email protected] build
> next build

info  - Checking validity of types
info  - Creating an optimized production build .node:events:368
      throw er; // Unhandled 'error' event
      ^

Error: EPERM: operation not permitted, open 'C:\Users\hp\Desktop\reactJs-project\NextJs\test-app\.next\trace'
Emitted 'error' event on WriteStream instance at:
    at emitErrorNT (node:internal/streams/destroy:157:8)
    at emitErrorCloseNT (node:internal/streams/destroy:122:3)
    at processTicksAndRejections (node:internal/process/task_queues:83:21) {    
  errno: -4048,
  code: 'EPERM',
  syscall: 'open',
  path: 'C:\\Users\\hp\\Desktop\\reactJs-project\\NextJs\\test-app\\.next\\trace'
}

so I just want to know is there any way to solve this problem?

Are you currently running the app in dev? If yes, cancel that process and try to build it again. Most likely the build is not able to access the trace due to being open by the dev process. — Koronag
– Koronag, Commented Apr 13, 2022 at 4:45

Steve Chambers · Accepted Answer · 2023-04-10 08:06:19Z

74

Posting comment from Koronag as an answer (as it helped me with this error and seems the most likely cause)...

This error is commonly seen when running a build while the dev server is already running.

E.g. in my case, I had a local build running via npm run dev and was trying to commit/push code, which invoked a Git Hook that also runs npm run dev.

edited Apr 10, 2023 at 8:06

answered Jul 18, 2022 at 15:47

Steve Chambers

39.8k29 gold badges178 silver badges222 bronze badges

Sign up to request clarification or add additional context in comments.

3 Comments

Raydot Over a year ago

Yep. Rookie mistake, but I made it.

Anupam Jan 11 at 0:40

I wasted 3 hours fighting this 😭

Toby Smith Apr 20 at 17:52

For those with a Next.JS app in an Nx monorepo, I've also found that stopping the Nx daemon with nx daemon --stop can resolve this issue.

Ashutosh Dash · Accepted Answer · 2023-08-16 06:24:55Z

7

In my case, npm run dev was running in another terminal. I closed that and rerun the command. It worked fine.

answered Aug 16, 2023 at 6:24

Ashutosh Dash

6842 gold badges11 silver badges18 bronze badges

Comments

Chris Plesniak · Accepted Answer · 2022-08-10 22:59:13Z

5

For me, it works fine this answer drives me to the resolver. I run 2 scripts in terminals:

once for development
another for the build process.

So after killing the development script it looks perfectly fine!

answered Aug 10, 2022 at 22:59

Chris Plesniak

1091 gold badge2 silver badges5 bronze badges

Comments

Deepak Thakur · Accepted Answer · 2023-06-14 05:28:38Z

4

This also happen if your website is running on IIS. To run the dev server from terminal (code editor), stop the server on IIS and the error will go away.

answered Jun 14, 2023 at 5:28

Deepak Thakur

1114 bronze badges

Comments

rizkyhaksono · Accepted Answer · 2024-01-12 18:57:59Z

3

Stop the server development, and try to build again. It works on me

Or if you want to force it (using Typescript) you can see on next docs right here https://nextjs.org/docs/app/api-reference/next-config-js/typescript

answered Jan 12, 2024 at 18:57

rizkyhaksono

412 bronze badges

2 Comments

Community Over a year ago

Your answer could be improved with additional supporting information. Please edit to add further details, such as citations or documentation, so that others can confirm that your answer is correct. You can find more information on how to write good answers in the help center.

Ram Chander Over a year ago

While this link may answer the question, it is better to include the essential parts of the answer here and provide the link for reference. Link-only answers can become invalid if the linked page changes. - From Review

Siddartha Pogula · Accepted Answer · 2024-06-11 16:11:06Z

2

this error arises, when you are running the application in local. ->like you were doing this

"npm run dev" in one terminal and in another termianl -> you were trying to build the application for some use. "npm run build" so this won't work, and this will give the above error.

to solve, stop the running application in local then run "npm run build"

thanks.

answered Jun 11, 2024 at 16:11

Siddartha Pogula

211 bronze badge

Comments

rizkyhaksono · Accepted Answer · 2024-09-04 08:01:20Z

1

This cause because your development mode is running, try to CTRL + C to close. And then start npm run build again.

answered Sep 4, 2024 at 8:01

rizkyhaksono

412 bronze badges

Comments

Isaac · Accepted Answer · 2022-05-26 13:41:22Z

0

From next-sitemap repo README.md

"Having next-sitemap command & next-sitemap.js file may result in file opening instead of building sitemaps in windows machines.

As a solution to this, it is now possible to use a custom config file instead of next-sitemap.js. Just pass --config .js to build command."

Next-Sitemap README.md - Building Sitemaps

The above worked for me

answered May 26, 2022 at 13:41

Isaac

1

Comments

PolyBlend Solutions · Accepted Answer · 2024-06-07 09:21:01Z

0

I solve this error. In my case, I had a local build running via npm run dev and was trying to commit/push code, which invoked a Git Hook that also runs npm run dev.

answered Jun 7, 2024 at 9:21

PolyBlend Solutions

12 bronze badges

Comments

mohammad khakshoor · Accepted Answer · 2024-11-11 09:20:59Z

0

you need to kill the ports that the app was running on them in the dev mode.

you can use the command : npx kill-port <port> like npx kill-port 3000

also you can combine the ports to terminated them at once like : npx kill-port 3000 3001 3002 3003

edited Nov 11, 2024 at 9:20

answered Nov 11, 2024 at 9:20

mohammad khakshoor

13 bronze badges

Comments

Kamrul Hasan Rafi · Accepted Answer · 2024-11-11 15:25:54Z

0

For my perspectation, I just terminated my current terminal and then reopen my project and then just commanded "npm run build" in my terminal again, Problem solved!

answered Nov 11, 2024 at 15:25

Kamrul Hasan Rafi

412 bronze badges

Comments

Kristal Pithwa · Accepted Answer · 2025-03-12 11:07:24Z

0

Kill the dev terminal then again run the npm run build

answered Mar 12 at 11:07

Kristal Pithwa

12 bronze badges

Comments

DungGramer · Accepted Answer · 2025-03-26 07:42:38Z

0

You need to enable Windows Developer Mode so that Preconstruct can create symlinks - https://www.howtogeek.com/292914/what-is-developer-mode-in-windows-10/

answered Mar 26 at 7:42

DungGramer

2,4061 gold badge10 silver badges15 bronze badges

Comments

John Fáwọlé · Accepted Answer · 2025-01-21 12:12:13Z

-1

You got this error because you were running quite too many processes simultaneously.

Simple solution that works for me: whenever you get this error, close your VS Code and open it again.

It works all the time. Hope this helps!

answered Jan 21 at 12:12

John Fáwọlé

11 bronze badge

1 Comment

Shaze Jan 23 at 12:13

Not necessary, it could be due to permission issue as well. Please refrain from providing answers without getting the full context. And please follow community guidelines. Thanks.

Bhuwan Darai · Accepted Answer · 2025-09-28 17:18:01Z

-1

Try updating your nodejs using nvm and then try building it. It solved in my case.

answered Sep 28 at 17:18

Bhuwan Darai

1

1 Comment

ryanwebjackson Sep 28 at 17:47

This does not provide an answer to the question. To critique or request clarification from an author, leave a comment below their post. - From Review

Collectives™ on Stack Overflow

Next JS : Error: EPERM: operation not permitted, open

15 Answers 15

3 Comments

Comments

Comments

Comments

2 Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

1 Comment

1 Comment

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

15 Answers 15

3 Comments

Comments

Comments

Comments

2 Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

1 Comment

1 Comment

Your Answer

Sign up or log in

Post as a guest

Linked

Related