Can you please ensure your package.json is looking specifically for files rather than a directory, or provide myself and my colleague @VladimirM with a copy of your package.json via a DM?
We are not able to determine the cause based on the files you provided as we don’t see the directories referenced in them.
We might need access to your repo though that is out of scope, and this point I can’t guarantee we’ll find an answer, but if there’s anyway we can view the repo, let us know.
I’ve noticed the following: When I use polling with a value of 1000 for the regular watcher, the error doesn’t occur.
However, I couldn’t find a way to set up polling for the webpack-dev-server watcher. But what exactly does polling have to do with watching certain files?
Unfortunately, we haven’t been able to determine what’s causing this from our side. It appears to be specific to Webpack and its configuration. My guess is that because module.exports doesn’t specify a list of files to watch, it’s defaulting to trying to watch every file on the pod - possibly because it’s looking at root (/) instead of the application root (./).
I don’t think we’ll be able to give this a proper answer though, because we lack detailed information on how Webpack is actually functioning in this way, and we haven’t been able to replicate this behavior. You may wish to reach out to them, if only to get more information on how exactly it tries to apply its settings in this context.