Error: Aborted because ... is not accepted

[sahanarula]

The app is not accepting the update and throws a warning Error: Aborted because ... is not accepted

webpack.config

module.exports = {
  "entry": ["whatwg-fetch", "babel-polyfill", "./app/app.js"],

  "stats": {
      "colors": false,
      "modules": true,
      "reasons": true
  },

  "failOnError": true, 

  "resolve": {
    "extensions": ['.js', '.jsx', '.json']
  },

  "module": {
    "loaders": [
      {
        "test": /\.jsx?$/,
        "exclude": /node_modules/,
        "loaders": ["babel-loader"]
      }
    ]
  },
}

grunt config

  {
      "webpack": _.extend(_.clone(webpackConfig), {
        "output": {
            "path": __dirname,
            "filename": "abc.js",
            "publicPath": "http://localhost:8080/",
        }
      }),

      "contentBase": __dirname + "/../../app",
      "filename": "abc.js",
      "inline": true,
      "hot": true,
    }

Expected Behavior

The app should update only selective components based on the HMR update.

Current Behavior

It reloads after throwing the above mentioned warning.

Your Environment

software	version
webpack	2.2.1
grunt-webpack	3.0.0-beta.1
grunt	1.0.1
node	4.3.0
npm	2.14.12
Operating System	macOS Sierra

[danez]

Can you try if this is fixed with 3.0.0-beta.1 ? We fixed a lot of stuff with the dev-server.
https://github.com/webpack-contrib/grunt-webpack/releases/tag/v3.0.0-beta.1

[sahanarula]

I already tried it with 3.0.0-beta.1

[danez]

Ok I digged into this problem a little bit and was able to reproduce this, but not only with grunt-webpack, but also with webpack-dev-server itself.
Depending on how you use hot reloading you may need to modify your entrypoint and add

if (module.hot)
  module.hot.accept()

From: webpack/webpack-dev-server#395 (comment)

Let me know if that helps.

[danez]

Closing for now, please reopen if you can reproduce with grunt-webpack but not with webpack-dev-server cli.