Updating app.js causes webpack dev server to report error and then reload the page

If you are reporting a bug, please fill in below. Otherwise feel free to remove this template entirely.

Can you reproduce the problem with latest npm?

yes

Many errors, especially related to “missing modules”, are due to npm bugs.

If you’re using Windows, follow these instructions to update npm.

If you’re using OS X or Linux, run this to update npm:

npm install -g npm@latest

cd your_project_directory
rm -rf node_modules
npm install

Then try to reproduce the issue again.

Can you still reproduce it? yes

Description

from a clone of master branch, running npm start launches webpack dev server as expected. making a simple text change to app.js in the template folder causes an error to occur in webpack dev server.

"Aborted because 191 is not accepted
Update propagation: 191 -> 130 -> 302"

stack:

"Error: Aborted because 191 is not accepted
Update propagation: 191 -> 130 -> 302
    at hotApply (http://localhost:3000/static/js/bundle.js:432:30)
    at hotUpdateDownloaded (http://localhost:3000/static/js/bundle.js:285:13)
    at hotAddUpdateChunk (http://localhost:3000/static/js/bundle.js:265:13)
    at webpackHotUpdateCallback (http://localhost:3000/static/js/bundle.js:8:12)
    at http://localhost:3000/0.e5484019108a9e1efba9.hot-update.js:1:1"

Expected behavior

no error should occur in this case.

Actual behavior

see above.

Environment

Run these commands in the project folder and fill in their results:

1. npm ls react-scripts (if you haven’t ejected): 0.9.4
2. node -v: 6.9.2
3. npm -v: 3.10.9

Then, specify:

1. Operating system: os x 10.12.3
2. Browser and version: chrome 56.0.2924.87

Reproducible Demo

Please take the time to create a new app that reproduces the issue.

Alternatively, you could copy your app that experiences the problem and start removing things until you’re left with the minimal reproducible demo.

(Accidentally, you might get to the root of your problem during that process.)

Push to GitHub and paste the link here.

By doing this, you’re helping the Create React App contributors a big time! Demonstrable issues gets fixed faster.

this is in the current master branch.

[Timer]

Released v1.0.11, @justingrant! Please give it a go.

[ugavnholt]

Workaround is to open the developer tools in chrome, and the exception is no longer thrown - it doesn’t have to stay open - still annoying though