Daniel Stout

@enyo will this PR get merged? I'm seeing the issue it describes - upload a portrait oriented image with resizeWidth specified and it ends up being incorrect in the processed...

I'm seeing this as well. Looks like it might have been fixed in https://github.com/dropzone/dropzone/pull/2001 but that PR hasn't been merged and I don't see an NPM package for it.. Edit:...

Using `zip-stream` directly instead of `archiver` fixed this for me. I created my own function: ``` zipAppend(zip, data, opts) { return new Promise((resolve) => { zip.entry(data, opts, (err) => {...

My fix was to stop using `domtoimage` and use `html2canvas` instead.

I really recommend just using `html2canvas` - it's more customizable, faster, and reliable. No need to generate the image multiple times, all elements are included in the first one. (I'm...

Here's a sample project demonstrating the issue: https://github.com/DanielStout5/WebpackLibraryHMRIssue It looks like it might be caused by the combination of the dev server and optimization.splitChunks. The project in question above is...

That configuration is set by Vue-CLI. My workaround was to delete the optimization section entirely when running in dev mode: ``` if (process.env.NODE_ENV == "development") { delete config.optimization; } ```

Yeah I figured it was a bit of an unusual configuration/setup. Is webpack-dev-server not expected to work with optimization turned on? Because disabling the optimization does fix the issue that...

Hmm.. Specifying client: false (and hot: false) doesn't seem to prevent all the dev-server additions. E.g.: ``` devServer: { client: false, hot: false }, ``` That does remove the hot/dev-server...

No dice unfortunately. With both client and hot set to false, it still adds the `__webpack_require__("./node_modules/webpack-dev-server...` line