Add watch-content-base option to Webpack-1

[charlespwd]

Please check if the PR fulfills these requirements

• An example has been added or updated in examples/ (for features)
• Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce?

• Feature

What is the current behavior? (You can also link to an open issue here)
Content-base changes, nothing happens #350

What is the new behavior?
Content-base changes, app reloads.

Does this PR introduce a breaking change?

• No

Other information:

I want those features in webpack-1 as well :)

Fixes #350

[SpaceK33z]

Hmm honestly I don't want to add features to 1.x anymore, and just want to focus on getting 1.x as stable as possible.

I would recommend to use webpack v2, but don't use the caret ^. By setting it to one version specifically it can't break suddenly (since it's still in beta).

[charlespwd]

But that's the thing. Webpack 2 is in beta. Which means anyone that uses it at work won't be able to use this feature until Webpack 2 is out of beta.

[Pyrolistical]

this branch isn't working for me. when I try to use this feature I get the error:
Error: ENOENT: no such file or directory, open '/Users/me/my-project/node_modules/webpack-dev-server/client/live.bundle.js'

i am using the options:
webpack-dev-server --progress --colors --inline --history-api-fallback --host 0.0.0.0 --content-base development/ --watch-content-base

[SpaceK33z]

@Pyrolistical you need to run npm run prepublish.

[pelx]

will it fix this problem?

Mixed Content: The page at 'https://xxxxxxx.c9users.io/' was loaded over HTTPS, but requested an insecure script 'http://xxxxx.c9users.io:3808/webpack/application.js'. This request has been blocked; the content must be served over HTTPS.

rgds

[SpaceK33z]

@pelx, no, that's a different problem ;).

Closing this for reasons stated above.

It won't take long anymore for the webpack v2 release.