Build Error on windows Error: EPERM: operation not permitted, scandir 'C:\Users\admin\Application Data'

[vatoer]

Summary

I need to build my project on Windows 11

I run

pnpm build

and got error

 next build

   ▲ Next.js 14.1.0
   - Environments: .env

   Creating an optimized production build ...
glob error [Error: EPERM: operation not permitted, scandir 'C:\Users\admin\Application Data'] {
  errno: -4048,
  code: 'EPERM',
  syscall: 'scandir',
  path: 'C:\\Users\\admin\\Application Data'
}
Failed to compile.

Error: EPERM: operation not permitted, scandir 'C:\Users\admin\Application Data'


> Build failed because of webpack errors
 ELIFECYCLE  Command failed with exit code 1.

how to solve it? thanks

Additional information

## environment 

- windows 11
- Next.js 14.1.0
- pnpm 8.9.0

on Windows 11 it should be 'C:\Users\admin\AppData\ right ? 

so how to change  'C:\Users\admin\Application Data' to 'C:\Users\admin\AppData\ ?

Already tried with npm and also yarn, it gives same error.

Example

No response

[icyJoseph]

I think this is because of missing permissions? Like the build command is not allowed to write to that directory.

I am not sure if in Windows Application Data requires some kind of admin level access. Try to move the project to Documents or something like that, that'd require less privileges.

[vatoer]

I'm using admin account,

I find the culprit,

its because my Prisma setting, I'm using custom location, I'll try to post in Prisma discussion

just in case someone find same problem

on my schema.prisma

./prisma/my-db/schema.prisma

generator client {
  provider = "prisma-client-js"
  output   = "  output   = "./generated/client""
}

[rhiskey]

I'm using admin account,

I find the culprit,

its because my Prisma setting, I'm using custom location, I'll try to post in Prisma discussion

just in case someone find same problem

on my schema.prisma

./prisma/my-db/schema.prisma

generator client {
  provider = "prisma-client-js"
  output   = "  output   = "./generated/client""
}

Just about half-year of waiting I ended up with cutting out this feature. Just don't use outputs with Prisma if you wish to build locally. I don't know why Prisma cant get access to those folders and why it is requested.

[itsnur-co]

I'm using admin account,

I find the culprit,

its because my Prisma setting, I'm using custom location, I'll try to post in Prisma discussion

just in case someone find same problem

on my schema.prisma

./prisma/my-db/schema.prisma

generator client {
  provider = "prisma-client-js"
  output   = "  output   = "./generated/client""
}

worked for me

[yf-hk]

I'm using admin account,
I find the culprit,
its because my Prisma setting, I'm using custom location, I'll try to post in Prisma discussion
just in case someone find same problem
on my schema.prisma
./prisma/my-db/schema.prisma

generator client {
  provider = "prisma-client-js"
  output   = "  output   = "./generated/client""
}

worked for me

Are you using Mac/Linux or Windows? It only happens on Windows

[karuppusamy-d]

Adding generated prisma output directory to experimental.outputFileTracingIgnores in next config.js solves the issue.

next config.js

experimental: {
    outputFileTracingIgnores: ["./generated/client/**/*"],
}

[doiali]

Adding generated prisma output directory to experimental.outputFileTracingIgnores in next config.js solves the issue.

next config.js

experimental: {
    outputFileTracingIgnores: ["./generated/client/**/*"],
}

I used this fix and it made some progress. Now the error has changed to this:

Error: EPERM: operation not permitted, scandir 'C:\Users\admin\Cookies'

I can't understand why!

[karuppusamy-d]

Update prisma output directory to '../node_modules/.prisma/client'

[Aibd]

You are really a genius

[zchdoc]

Delete "import os from 'os'" and other imports related to system operations.

or delete the fold : C:\Users\admin\Application Data

the fold size is zero

but all the unread zero size file or fold may ouput the error.....

i delete the code

// import os from 'os'
....
// const homeDir = os.homedir()

now It works well ，again

[cupid20103]

This is incorrect, I think

[auziqni]

no it doesnt work
i try this on fresh app, no import except prisma
i dont even have folder "Application Data"

[cupid20103]

On the schema.prisma, please remove the output option and write code like this

generator client {
  provider = "prisma-client-js"
}

If so, your code works well. I think

[dikshantsingh510]

Thanks, it works for me.
And update prisma client import from "@prisma/client" in lib/prisma.ts file. like 👇👇👇

import { PrismaClient } from "@prisma/client";

[gilmartatho]

Thanks for all.

[AzizOzenir]

When I moved project to c: disk, removed .next and node_modules folder and reinstall packages then it fixed

[yf-hk]

Well, this is clearly a Next.js bug. Their poor code quality and the usage of weback worries me.

[inuka-mayakaduwa]

Worked for me, thankyou !

[Kimlong168]

it works for me

[mohammad-khoddami]

It works fine.

[AzizOzenir]

Well, this is clearly a Next.js bug. Their poor code quality and the usage of weback worries me.

its probable potential cause.

[devSubham35]

I faced the same issue and here’s how I ✅ solved it 👇
⚠️ Note: After doing this changes please remove .next folder
and run prisma command yarn prisma generate then yarn build (in my case i use yarn)

Solution 1 -> Basically, the Prisma output generated file path should be changed to "/node_modules/prisma/client".

/// In your schema.prisma file, update the generator block like this:

/// before
generator client {
  provider = "prisma-client-js"
  output   = "../lib/generated/prisma"
}

/// after
generator client {
  provider = "prisma-client-js"
  output   = "../node_modules/prisma/client"
}

Solution 2 -> In the prisma client instance file just change the import part

/// before
import { PrismaClient } from "./generated/prisma";

/// after
import { PrismaClient } from "@prisma/client";

const globalForPrisma = global as unknown as { prisma: PrismaClient };
export const prisma = globalForPrisma.prisma || new PrismaClient();
if (process.env.NODE_ENV !== "production") {
  globalForPrisma.prisma = prisma;
}

⚠️ Note: This issue only occurs on Windows, not on Linux.

[beautifulcoder]

Changing the Prisma client to @prisma/client works for me but this feels hacky as hell. At least I am able to get compiler feedback in local.