Watchpack Error (initial scan): Error: EACCES: permission denied, lstat '/mnt/c/DumpStack.log.tmp'

[shivayan-bora]

What version of Next.js are you using?

11.0.1

What version of Node.js are you using?

v14.17.3

What browser are you using?

Chrome

What operating system are you using?

WSL 2 for Windows 10

How are you deploying your application?

next dev

Describe the Bug

I am starting with the Next.js Official Tutorial and I encountered this issue while running the application on my WSL2 Windows terminal. I ran the following command:

npx create-next-app nextjs-blog --use-npm --example "https://github.com/vercel/next-learn-starter/tree/master/learn-starter"

On Running npm run dev, I get the following error messages:

╭─shivayanbora123 at LAPTOP-5T2N7GCS in /mnt/c/GithubRepos/nextjs-blog on main✔ 21-07-25 - 15:50:33
╰─⠠⠵ npm run dev

> learn-starter@0.1.0 dev /mnt/c/GithubRepos/nextjs-blog
> next dev

ready - started server on 0.0.0.0:3000, url: http://localhost:3000
info  - Using webpack 5. Reason: Enabled by default https://nextjs.org/docs/messages/webpack5
Watchpack Error (initial scan): Error: EACCES: permission denied, lstat '/mnt/c/DumpStack.log.tmp'
Watchpack Error (initial scan): Error: EACCES: permission denied, lstat '/mnt/c/hiberfil.sys'
Watchpack Error (initial scan): Error: EACCES: permission denied, lstat '/mnt/c/pagefile.sys'
Watchpack Error (initial scan): Error: EACCES: permission denied, lstat '/mnt/c/swapfile.sys'
event - compiled successfully
Watchpack Error (initial scan): Error: EACCES: permission denied, lstat '/mnt/c/DumpStack.log.tmp'
Watchpack Error (initial scan): Error: EACCES: permission denied, lstat '/mnt/c/hiberfil.sys'
Watchpack Error (initial scan): Error: EACCES: permission denied, lstat '/mnt/c/pagefile.sys'
Watchpack Error (initial scan): Error: EACCES: permission denied, lstat '/mnt/c/swapfile.sys'

The server does start up, but the fast refresh doesn't work because of which for any change, I need to restart my server. I initially thought it might be something related to the Tutorial application. So I created a new Next.js application using the command:

npx create-next-app nextjs-app

But this resulted in the same error.

Expected Behavior

1. The error shouldn't come up
2. Fast Refresh should work else, it becomes very difficult to go through the process of creating a Next.js App

To Reproduce

While using WSL2 for Ubuntu, run the command:

npx create-next-app nextjs-blog --use-npm --example "https://github.com/vercel/next-learn-starter/tree/master/learn-starter"

Then go into the folder and run npm run dev. After that make any changes to the pages/index.js and refresh the page. It doesn't pick up the changes. Then restart the server to see the changes getting picked up.

[markhughes]

This is due to Webpack 5's broken Watchpack. From a quick glance there are a bunch of work arounds in this issue but even after apply them the nextjs project does not refresh. Not sure whats different in nextjs.

webpack/watchpack#187

[markhughes]

For a temporary workaround, add webpack5: false, to your nextjs config

[mariohmol]

Hi there, still with this issue on WSL ubuntu, but now when I do webpack5 it gives me the error

Error: Webpack 4 is no longer supported in Next.js. Please upgrade to webpack 5 by removing "webpack5: false" from n

Any updates on this?

[mariohmol]

For those who get's here, follow: webpack/watchpack#187 (comment)

[pebcakerror]

I understand the underlying issue is with webpack. But I would like to see Next.js address this if webpack won't. My first experience with Next.js was to get an error trying to access system files at the same time it mentions telemetry. Was ready to chuck Next.js then and there if they were trying to read sensitive system files for telemetry.

Ended up in long meeting with our corporate security team to make sure some bad actor in the dependency chain didn't just steal a bunch of information.

$ npm run dev

> dev
> next dev

ready - started server on 0.0.0.0:3000, url: http://localhost:3000
Watchpack Error (initial scan): Error: EACCES: permission denied, lstat '/mnt/c/DumpStack.log.tmp'
Watchpack Error (initial scan): Error: EACCES: permission denied, lstat '/mnt/c/hiberfil.sys'
Watchpack Error (initial scan): Error: EACCES: permission denied, lstat '/mnt/c/pagefile.sys'
Watchpack Error (initial scan): Error: EACCES: permission denied, lstat '/mnt/c/swapfile.sys'
event - compiled successfully in 14.8s (159 modules)
Watchpack Error (initial scan): Error: EACCES: permission denied, lstat '/mnt/c/DumpStack.log.tmp'
Watchpack Error (initial scan): Error: EACCES: permission denied, lstat '/mnt/c/pagefile.sys'
Watchpack Error (initial scan): Error: EACCES: permission denied, lstat '/mnt/c/hiberfil.sys'
Watchpack Error (initial scan): Error: EACCES: permission denied, lstat '/mnt/c/swapfile.sys'
Attention: Next.js now collects completely anonymous telemetry regarding usage.
This information is used to shape Next.js' roadmap and prioritize features.
You can learn more, including how to opt-out if you'd not like to participate in this anonymous program, by visiting the following URL:
https://nextjs.org/telemetry

[github-actions]

Please verify that your issue can be recreated with next@canary.

Why was this issue marked with the please verify canary label?

We noticed the provided reproduction was using an older version of Next.js, instead of canary.

The canary version of Next.js ships daily and includes all features and fixes that have not been released to the stable version yet. You can think of canary as a public beta. Some issues may already be fixed in the canary version, so please verify that your issue reproduces by running npm install next@canary and test it in your project, using your reproduction steps.

If the issue does not reproduce with the canary version, then it has already been fixed and this issue can be closed.

How can I quickly verify if my issue has been fixed in canary?

The safest way is to install next@canary in your project and test it, but you can also search through closed Next.js issues for duplicates or check the Next.js releases.

My issue has been open for a long time, why do I need to verify canary now?

Next.js does not backport bug fixes to older versions of Next.js. Instead, we are trying to introduce only a minimal amount of breaking changes between major releases.

What happens if I don't verify against the canary version of Next.js?

An issue with the please verify canary that receives no meaningful activity (e.g. new comments that acknowledge verification against canary) will be automatically closed and locked after 30 days.

If your issue has not been resolved in that time and it has been closed/locked, please open a new issue, with the required reproduction, using next@canary.

I did not open this issue, but it is relevant to me, what can I do to help?

Anyone experiencing the same issue is welcome to provide a minimal reproduction following the above steps. Furthermore, you can upvote the issue using the 👍 reaction on the topmost comment (please do not comment "I have the same issue" without repro steps). Then, we can sort issues by votes to prioritize.

I think my reproduction is good enough, why aren't you looking into it quicker?

We look into every Next.js issue and constantly monitor open issues for new comments.

However, sometimes we might miss one or two due to the popularity/high traffic of the repository. We apologize, and kindly ask you to refrain from tagging core maintainers, as that will usually not result in increased priority.

Upvoting issues to show your interest will help us prioritize and address them as quickly as possible. That said, every issue is important to us, and if an issue gets closed by accident, we encourage you to open a new one linking to the old issue and we will look into it.

Useful Resources

• How to Contribute to Open Source (Next.js)
• How to create a Minimal, Complete, and Verifiable example
• Reporting a Next.js bug
• Next.js Triaging issues

[balazsorban44]

This issue has been automatically closed because it wasn't verified against next@canary. If you think it was closed by accident, please leave a comment. If you are running into a similar issue, please open a new issue with a reproduction. Thank you.

[github-actions]

This closed issue has been automatically locked because it had no new activity for a month. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.