This issue is in regards to sage 9.0.0-beta.4 and Docker for Windows.
Up to this point I’ve been using Sage 9 inside Docker for Mac containers and it’s been running well. I’m looking to expand its usage to a few of my team members and in doing so I’ve begun testing different environments, specifically Docker for Windows.
File changes are not seen or compiled in Docker for Windows unless they originate from within the container. This suggests a polling issue.
I initially added polling support to the Webpack configuration but it did not fix the problem. After some additional tinkering I found that the problem does not originate with Webpack core but instead from either browsersync-webpack-plugin or one of its dependencies.
If you remove BrowserSyncPlugin from the watch configuration then Webpack will successfully compile new changes provided that polling support is added to Webpack’s watchOptions. This means that you have to manually reload the page to see those changes, so it’s not the end of the world; however, BrowserSyncPlugin definitely improves the development experience and it would be nice to have.
The browsersync-webpack-plugin library allows you to pass in additional BrowserSync options, and if given a watchOptions object (separate from Webpack’s watchOptions object) then BrowserSync will pass those options to Chokidar, its fs event system wrapper. Chokidar will poll for changes only if provided a ‘usePolling: true’ property.
I suspect that this is where the issue lies. Has anyone experienced a similar issue and found the solution? I’ve included the usePolling property inside the BrowserSyncPlugin object to no avail.