Feature request: expose errors to plugins

[tiye]

By now errors in Webpack is handled like this, an error message:

        errors: function(errors) {
            status.text("App updated with errors. No reload!");
            okness.text("Errors while compiling.");
            $errors.text("\n" + stripAnsi(errors.join("\n\n\n")) + "\n\n");
            header.css({borderColor: "#ebcb8b"});
            $errors.show(); iframe.hide();
        },

If that code is exposed then we may get error messages like this with plugins, and it can be quite convenient, as it already was in ClojureScript projects.

---

update:

I made a prototype https://github.com/mvc-works/webpack-hud

[SpaceK33z]

Did you look at #542? It has a nice example of how to listen to socket changes. Bit hacky, but it works.

That's probably only a temporary solution though. Any feedback on how you want this exposed would be helpful.

[SpaceK33z]

I exposed some events to the window now with 06c7773. An example of how to use it:

window.addEventListener('message', function onWebpackMessage (msg) {
    if (!msg.data || !msg.data.type) return;
    switch(msg.data.type) {
        case 'webpackOk':
            console.log('bundle compiled ok');
            break;
        case 'webpackErrors':
            console.log('There were some errors', msg.data.data);
            break;
    }
}, false);

Let me know if you have any feedback. It's not released yet.

[tiye]

Looks good to me https://github.com/mvc-works/webpack-hud/tree/with-new-api

Still want to ask if I can get the stripped string, since in the browser people are unlikely to need ANSI escape code. Then I should not need to strip by myself:

const errorMsg = webpackMsg.data.map((s) => stripAnsi(s)).join('\n');

[SpaceK33z]

Sure, can you make a PR for that? Busy atm.

[SpaceK33z]

Closing this since the feature has been implemented. Let me know if you don't like the API or want to make some changes.