Issues with async resolve about react-async-component HOT 2 OPEN

OK so our problem was that the webpack boilerplate chunk hash was not being updated when the chunk contents changed. We were using webpack-md5-hash which is being used in react-universally.
See this issue for details: erm0l0v/webpack-md5-hash#9
Also: webpack/webpack#1856

We discovered that people were getting two versions of the same file. When we purged the cache on both fastly and cloudflare everything went back to normal.

We removed webpack-md5-hash from our project and using HashedModuleIdsPlugin and ChunkManifestWebpackPlugin and did a similiar thing as found here:
ctrlplusb/react-universally#472

See webpack’s caching guide here: https://webpack.js.org/guides/caching/

Hope this helps somebody 🙈

from react-async-component.

We just had the exact same experience! Also code splitting routes. Only happens on production with a similar setup.
We had to back out as well. This was our second attempt at this after having a similar experience with faceyspacey/react-universal-component

Our error was: Cannot read property 'call' of undefined

from react-async-component.