4.40.3: Surface HTTP error statuses in the browser fetch loader

Fixed

• The browser fetch loader now rejects with Could not fetch file: <status>
  on 4xx/5xx HTTP responses (except 416, which the length: 'auto' loop
  still consumes as a fall-back signal) instead of feeding the error body to
  the parser and surfacing a misleading Invalid image format error. This
  brings the browser path in line with the Node path. Both the browser and
  Node loaders now reject with an Error object (the Node path previously
  rejected with a plain string).

Full Changelog: v4.40.2...v4.40.3