Closed LastStranger closed 5 years ago
this problem has been bothering me for many days, please help me out
You can definitely have folders in your clean target. This looks like a permissions issue at first glance.
How to define it? I can't find any clue in the docs
The issue is most likely with windows filesystem. There is a long history of EPERM errors with rimraf.
It is also possible you are having legitimate permission errors like @johnagan suggested, but if subsequent cleans are successful, this seems unlikely. How are you starting/stopping the build? Are you doing it inside vscode?
Is it possible for you to create a minimal reproducible repository with exact instructions how to reproduce?
It's really weird, I come back to my project after a few days, this problem seems solved automatically, but I'll keep watching, once this problem shows up again, I'll create a repository and let you know, thanks for the help
Thanks for the update @LastStranger. Reopen this issue later if you need to.
Issue description or question
this is my dist folder
when I npm run build, this plugin first show some errors like this and my css folder disappeared. then I npm run build again, same error and my js folder disappeared,
then I run it again, the process succeed. I wonder if I shouldn't have folders in my dist folder.
Webpack Config
Environment
win10, "webpack": "^4.30.0", "webpack-cli": "^3.3.0",, "clean-webpack-plugin": "^2.0.1",
Run:
npx envinfo --system --binaries --npmPackages clean-webpack-plugin,webpack