-
-
Notifications
You must be signed in to change notification settings - Fork 106
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Watch Mode stops functioning if emitted file is busy or locked #44
Comments
ping 🏓 This is such an irritating little issue, couldn't someone please take it up? 🙏 |
I agree, sometimes webpack takes a while to restart, having the watch restart by itself is important. |
I've had this problem for 2 weeks and finally found a solution, it may not be the case for everyone but I use OneDrive to save my files and coincidentally when i checked right after having the issue, OneDrive was uploading the damn file. So I just stopped OneDrive :P |
old issue, create a new issue if this is still an issue |
Do you want to request a feature or report a bug?
A bug
What is the current behavior?
When in watch mode, if a file is busy when attempting to emit to it, watch stops functioning. The following error is appropriately logged:
If the current behavior is a bug, please provide the steps to reproduce.
run webpack --watch
save a watched file
output to a file which is currently being used by another process
What is the expected behavior?
An error is logged to the console but watch mode continues to function. This is the behavior of Grunt and Gulp watchers.
Please mention other relevant information such as the browser version, Node.js version, Operating System and programming language.
A valid reason why a file could be momentarily busy is if it is being synced to a server directory.
--
Here are the details of my setup:
--
Moved from webpack/webpack#3523
The text was updated successfully, but these errors were encountered: