Do not overwrite the output.path

[gajus]

webpack-dev-server overwrites the output.path parameter of the user supplied config (gajus/write-file-webpack-plugin#1).

• User supplied config should be immutable.
• There is no reason to overwrite the output.path.
• This makes the original output.path value inaccessible from the plugin.

[gajus]

@sokra Any chance of this behaviour changing in 2.0.0?

[SpaceK33z]

This also caused the issue in #266, probably #473, and would be a good first step to fix #106.

@sokra, what's your opinion about this? I'd say that we should require output.path to be supplied by the user, and throw an error if it's not set. I'm note sure about the reason why it's there in the first place, so I don't feel comfortable removing this.

[sokra]

WDS doesn't use the output.path. But I think we could just remove the assignment and it should work fine.

The assignment was originally to enforce linux style paths, because the prev versions of memory-fs doesn't support windows style paths. But as it supports it now it should be fine to remove this.

[SpaceK33z]

@sokra, all right, I'll remove that in v2 then.

[SpaceK33z]

Removed it in the above commit. Performed a few tests with different setups in the examples/ dir, and everything still seems to work. Luckily we're running a beta anyway, so we can test this out on our beta users.

[codingleo]

Hey guys! I'm still having the same issue here.

Does the v2 is ready for npm? I'm also having the current versions:

"webpack-dev-server": "~1.16.2",
"webpack-dev-middleware": "~1.8.4"

And having the error:

[dsebastien]

Just to clarify for me: with Webpack 1.x we had to define outputPath in our devServer config so that we could have the resources written on disk (via write-file-webpack-plugin).

Can I now remove outputPath from my devServer config with Webpack 2 rc1 / webpack-dev-server 2 rc1 ?