However, I'm slightly confused (as a non safe-write user :P). Judging from this commit on January, 30th (which removes a similar warning from a previous section), it seems like the underlying problem has been fixed @ watchpack (concretely, thanks to this commit from September, 2015), and therefore this warning doesn't apply anymore for Webpack 2.
@bebraw Time to get rid of the warning altogether instead of fixing it?
This change aligns the book with Webpack docs, as seen @ https://webpack.github.io/docs/webpack-dev-server.html#working-with-editors-ides-supporting-safe-write.
However, I'm slightly confused (as a non safe-write user :P). Judging from this commit on January, 30th (which removes a similar warning from a previous section), it seems like the underlying problem has been fixed @ watchpack (concretely, thanks to this commit from September, 2015), and therefore this warning doesn't apply anymore for Webpack 2.
@bebraw Time to get rid of the warning altogether instead of fixing it?