Remove devServer.outputPath requirement

[chrisblossom]

Just a thought to make it less opinionated/remove devServer requirement when not using webpack-dev-server:

if (!compiler.options.output.path) {
    throw new Error('output.path is not defined.');
}

if (compiler.options.devServer && (compiler.options.devServer.outputPath !== compiler.options.output.path)) {
    throw new Error('output.path and devServer.outputPath must be equal.');
}

outputPath = compiler.options.output.path;

Readme could say something along the lines of "If using webpack-dev-server, devServer.outputPath must equal output.path."

[gajus]

First I will see if I can make webpack-dev-server change the behaviour on their end (webpack/webpack-dev-server#337). Will come back to this in about a week.

[gajus]

@chrisblossom v3.1.7 published.

[chrisblossom]

@gajus thank you!

[wyntau]

@gajus webpack-dev-server still overwrite output.path, so this plugin get error output.path when use compiler.options.output.path

And when I use this plugin in windows, all files are wrote to incorrect place

because path.sep in windows is \, so compiler.options.output.path is used incorrectly

[gajus]

@gajus webpack-dev-server still overwrite output.path, so this plugin get error output.path when use compiler.options.output.path

Have you read the usage docs?

https://github.com/gajus/write-file-webpack-plugin#usage

[gajus]

because path.sep in windows is , so compiler.options.output.path is used incorrectly

I am not familiar with windows. Can you submit a PR addressing the issue?

[wyntau]

OK. I will make a PR to solve this problem.