Accepted answer

Figured it out! I first ran webpack with --display-error-details, which in my opinion should just be on by default all the time. webpack --progress --color --watch --display-error-details.

This told me that the reason webpack was having such a hard time was because there was something wrong with the extensions I told it to look for:

  resolve: {
    extensions: ['.js', '.jsx'],

Would look for react.js.js and react.js.jsx instead of just react.js. So, I had to update that to:

  resolve: {
    extensions: ['', '.js', '.jsx'],

Which fixed it! =)

Related Query

More Query from same tag