Loader is not picking up changes when running webpack-dev-server programmatically

The recent patch #80 will make loader pick-up changes only when webpack-dev-server is invoked from CLI.

The following checks only process.argv but it should be also checking for programmaic use, when webpack-dev-server is used through Node.js API

  var hasWebpackDevServer = Array.prototype.filter.call(process.argv, function (arg) {
    return arg.indexOf('webpack-dev-server') !== -1;
  }).length > 0;

I would love to look in to that, but I’m not quite sure how to detect webpack-dev-server programmatic use. Any hints?

[halfzebra]

@eeue56 Thanks for the reply!

How about passing a flag via query string to tell loader to watch the files?

[baransu]

I’m using ejected create-react-app with additional this loader to use Elm with React any webpack seems to listen only for changes in directory specified in `elm-package.json’. Any change within nested folders and modules are silent and require force update with some change to not nested file.