Gerry Alvarez

@bestander Thank you for the link, it looks like yarn is a good alternative to consider! As for the issue I reported, I will continue looking into it. I tried...

I think `output.clean` does not clean the output directory when running webpack-dev-server, while this plugin seems to be able to.

I think this would be a great improvement! Per [my comment](https://github.com/jwaliszko/ExpressiveAnnotations/issues/48#issuecomment-298675140) on #48, I think a [UMD wrapper](https://github.com/umdjs/umd) in particular would be helpful to make this library compatible with modern...

This does not seem to be a misconfiguration your part. Related to #91 and https://github.com/NMFR/optimize-css-assets-webpack-plugin/issues/53#issuecomment-494830816.

Related to #91 and https://github.com/NMFR/optimize-css-assets-webpack-plugin/issues/53#issuecomment-494830816.

Perhaps related to https://github.com/NMFR/optimize-css-assets-webpack-plugin/issues/53#issuecomment-494830816, the plugin does not seem to respect general webpack configuration options related to source maps.

Related to #91.

Thank you for the feedback!

I also received this same error after assigning a value to the output property.

For whatever it's worth, this rule does make it harder to work with Visual Studio default file saving behavior. See: - https://stackoverflow.com/questions/5406172/utf-8-without-bom - https://developercommunity.visualstudio.com/content/problem/21744/vs2017-rc-breaks-the-encoding-of-my-files.html - https://developercommunity.visualstudio.com/content/problem/136180/utf-8-save-as-without-signature-default-request-to.html