• Can you put this code in an optional Plugin (JsonpErrorHandlingPlugin or similar)? I don't want to blow up the webpack runtime when you don't want error handling.
• You must not change the require.ensure interface. It's expected that the callback is only called when the chunk is loaded. But require.ensure has no error handling specified :(. Maybe we should return a Promise from require.ensure? (I'm open for ideas)
• use var a=1;var b=2; instead of var a=1,b=2;

• ok
• I think that require.ensure callback should always called and first arguments must be a Error or null, because it is a common behavior in callback style. But it breaks backward compatibility. As for the called only when the chunk is loaded, this code may simulate such behavior.

var
    defaultEnsure = __webpack_require__.e;

if (defaultEnsure) {
    __webpack_require__.e = function (chunk, callback, name) {
        defaultEnsure.call(null, chunk, function (error, _require) {
            if (!error) callback(_require);
        }, name);
    }
}

• ok

@sokra ?

I can take a look this evening...

This plugin looks really good, something I'm in need of. I wonder however if AMD support could be added without too much difficulty as, imo, AMD lends itself to error handling better than commonJS using this:

#758

require(['a'], function(a) {
    // success
}, function() {
    // error
});

I also wonder if it would be better to follow a similar signature for commonJS as that way it wouldn't be a breaking change:

require.ensure(['a'], function(require) {
    var a = require('a');    
    // success
}, function() {
    // error
});

The only slight complication would be the need to check the type of the third argument to determine if it's the 'name' or an error callback.

At work, I use a similar plug-in, but with a few changes. I saved the default order on arguments in require.ensure callback function for backward capability with webpack loaders and notify about timeout via window event. Tonight or tomorrow morning I can show it.

As for the interface require.ensure, I have come to believe that the best way is to return the Promise, but i don't know what to do for old browsers.

I personally am not so keen for promises in this situation as it's a massive departure from "standard" commonJS and AMD specifications.

I think require.ensure(name?, deps, successCallback, errorCallback) would be the best as it's analogous to AMD (require(name?, deps, successCallback, errorCallback)) so would keep things simple and familiar.

I've noticed require.async uses this format too.

It'd be good to see what you're using currently.

I think require.ensure(name?, deps, successCallback, errorCallback) would be the best as it's analogous to AMD

looks great... and this way we could keep backward compatiblity...

I've sent a pull request which adds support for the error callback when using require.ensure

#763

Any progress on this? I could use that too...

I wrote a plugin https://github.com/richardscarrott/require-error-handler-webpack-plugin which adds error handling to require.ensure, AMD and the bundle loader, it was relatively difficult to hook into all the right places so would be nice if we'd be able to either properly integrate this into webpack or open up a few more hooks to make this plugin cleaner.

Would be really useful if this merged

@indianburger as a temporal solution you could use this: https://github.com/NekR/async-module-loader
Works pretty well and in most cases you just need to replace bundle-loader with async-module-loader.

I've sent a pull request which adds support to Webpack v2.2 for the error callback when using require.ensure

#4069