webpack/lib/web
Rafal Chlodnicki b322070344 fix: provide useful stacktrace on chunk loading failure
Error created from load/error event handler has no useful stack trace
whatsoever as it's an async event and stack has unwound already at that
point.

To have better (sync) stacktrace of what triggered loading of the
chunk, create error before stack has unwound and use it and its
stacktrace later, in case of an error.

This potentially has some processing overhead as browser needs to
create a stacktrace. It's probably not that big though but I haven't
done any real testing.
2019-05-19 22:11:24 +02:00
..
FetchCompileWasmTemplatePlugin.js allow to disable wasm import mangle 2018-06-05 23:49:02 +02:00
JsonpChunkTemplatePlugin.js fixes #7577 2018-06-26 17:19:37 +02:00
JsonpExportMainTemplatePlugin.js use types from schema 2018-09-21 11:04:19 +02:00
JsonpHotUpdateChunkTemplatePlugin.js Destructure 'require' to improve readability 2018-03-22 12:05:58 +01:00
JsonpMainTemplate.runtime.js Use document.head instead of getElementsByTagName 2018-12-06 03:00:23 +03:00
JsonpMainTemplatePlugin.js fix: provide useful stacktrace on chunk loading failure 2019-05-19 22:11:24 +02:00
JsonpTemplatePlugin.js run prettier on existing code 2018-02-25 02:00:20 +01:00
WebEnvironmentPlugin.js refactor(WebEnvironmentPlugin): upgrade to ES6 (#3790) 2017-01-05 11:34:34 -06:00