Closed DongShi closed 5 years ago
actually find an answer myself https://stackoverflow.com/questions/52322913/webpack-4-devserver-hmr-plus-full-reload-on-other-file-changes-like-views/52476173
the solution mentioned in the SO post also applies to gaze.
Hi there. I have the following package.json scripts:
where in copy.js I setup some gaze watcher to monitor file changes, and if it happens, the new files would be copied to some folder. And ideally, webpack-dev-server would reflect the new changes.
Something like this:
However after I run npm start, it seems gaze would block the change at copy.js so my webpack-dev-server never gets started.
So gaze is a synchronized and blocking process? Is there any suggestion on how to handle this case? Put gaze in a child process?
Thanks