Loading chunk 1 failed.

Do you want to request a feature or report a bug?
bug

What is the current behavior?
On Internet Explorer 11, a request to a bundle in the cache results in “Loading chunk 1 failed.
If the current behavior is a bug, please provide the steps to reproduce.

  1. Visit a website with almost 100 bundle files in the dist folder (3 are 11-18mb in size)
  2. Visit the website a second time
  3. See the network shows the chunk loaded with a 304 status code
  4. See the console writes out a chunk failed (usually chunk 1)
{
"description": "Loading chunk 1 failed",
"message": "Loading chunk 1 failed.",
"name": "Error",
"stack": "Error: Loading chunk 1 failed.
  at PROMISE_THROWER (http://{domain-name}/{app-folder}/app/dist/bundle11152017111856.main.js:90254:42)
  at promiseReactionJob (http://{domain-name/{app-folder}/app/dist/bundle11152017111856.main.js:90279:9)
  at Anonymous function (http://{domain-name}/{app-folder}/app/dist/bundle11152017111856.main.js:90267:9)"
}

What is the expected behavior?
All bundles should load regardless if you have a status code of 304 (not modified)
If this is a feature request, what is motivation or use case for changing the behavior?

Please mention other relevant information such as the browser version, Node.js version, webpack version and Operating System.
(This works fine in Chrome and MS Edge)

Internet Explorer 11.1770.14393.0
Windows 10
npm 3.10.10
node 6.12.0
webpack@^3.8.1
es5-shim@^4.5.9
es6-shim@^0.35.3

Author: Fantashit

3 thoughts on “Loading chunk 1 failed.

  1. im on version ^4.6.0 and getting Error: Loading CSS chunk 2 failed. and it doesnt work on firefox… (ok on chrome, safari)

    the requested file is: static/css/home-page.6a695f91.chunk.js which get extracted as it refers to css. but i still have webpack trying to fetch this as a module…. somewhere…

Comments are closed.