Add outputPath as plugin option, override conditional checks

[ksrb]

This plugin seems to be a little broken?

This PR lets the sandbox work with [email protected] + [email protected].

I don't think this PR should necessarily be merged as it changes the API but I'm just highlighting the problem and a potential solution.

Additional Details

In webpack 1.x
I couldn't get the sandbox to work with [email protected] + [email protected] due to it throwing:

output.path is not. Define output.path.

In webpack 2.x
I couldn't get the sandbox to work with [email protected] + [email protected] due to it throwing:

Invalid configuration object. Webpack has been initialised using a configuration object that does not match the API schema.
...

There's clearly been a API change in webpack 2.x since the beta 😄 .

[odensc]

Ah - the newest version of this plugin only supports webpack 2.x, hence the major version change. The sandbox should be updated to reflect the version requirement.

[jkomusin]

I believe this will cause the plugin to fail if no outputPath option is specified (see the check below this). For backwards compatibility it may want to fall back to the original output.path of the compiler.

[jkomusin]

This would be a very helpful addition for us, as we organize different types of resulting bundles into sub-directories under the root Webpack output path. This flag would allow us to circumvent plugins that don't agree with that, like HotModuleReplacement which dumps hot-update files into the root output path.

[gajus]

Is this still relevant?

[odensc]

@gajus #37 fixed the error, but this could still be useful in the case you'd want write-file-webpack-plugin to write to a different path than output.path.

[gajus]

If the conflicts are resolved, I will merge it.