You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Here's the scenario: I start up webpack-dev-server and wait for my page to finish loading. Then I edit a .less file on my computer, it gets rsync'd into my Vagrant box where webpack-dev-server is running, WDS picks up the change and HMR refreshes my CSS without a full page reload. However, when I edit my .less again then nothing happens. Nothing is logged to Chrome's dev console, and WDS doesn't print anything to the terminal.
If I had to take a guess, I suspect rsync is recreating the file and that's destroying the [inotify?] watch. At least that would explain why it works once.
The text was updated successfully, but these errors were encountered:
Here's the scenario: I start up webpack-dev-server and wait for my page to finish loading. Then I edit a .less file on my computer, it gets rsync'd into my Vagrant box where webpack-dev-server is running, WDS picks up the change and HMR refreshes my CSS without a full page reload. However, when I edit my .less again then nothing happens. Nothing is logged to Chrome's dev console, and WDS doesn't print anything to the terminal.
If I enable polling,
then everything works fine.
If I had to take a guess, I suspect rsync is recreating the file and that's destroying the [inotify?] watch. At least that would explain why it works once.
The text was updated successfully, but these errors were encountered: