Skip to content
This repository was archived by the owner on May 1, 2020. It is now read-only.

Conversation

abomadi
Copy link
Contributor

@abomadi abomadi commented Apr 3, 2017

Prior to this patch, the script would only raise "internal" errors raised by webpack and skip "compilation" errors that could be caused by faulty config or source code. This is contrary
to what webpack suggests in terms of error handling[1].

This patch makes it so that any compilation errors will cause ionic to also abort the build, while any compilation warnings will log a warning through ionic's Logger.

[1] https://webpack.js.org/api/node/#error-handling

Prior to this patch, the script would only raise errors raised directly by webpack and skip errors raised from the compilation. This is contrary to what webpack suggests in terms of error handling[1]. This patch makes it so that any compilation errors will cause ionic to also abort the build, while any compilation warnings will log a warning through ionic's Logger.
@mburger81
Copy link
Contributor

@danbucholtz this could be useful, what do you think?

@danbucholtz danbucholtz self-assigned this Apr 17, 2017
@danbucholtz
Copy link
Contributor

I'll check this out when I get a chance.

Thanks,
Dan

@danbucholtz danbucholtz merged commit fa5e52c into ionic-team:master Apr 21, 2017
@kapilkarda
Copy link

Hello,
is it solve ?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

4 participants