Being able to throw error and break code instead of console.warn

[Martodox]

Hi.
I am building gulp build tool for my project and found out one feature that is missing.
We should be able to break the build if an error shows up.
Right now all errors are reported by console.warn function.
Wouldn't it be nice to be able to set a flag throwing errors or supply custom reporter for even better experience.

Let me know what do you think about a feature like that. If it comes with a positive response I'd be happy to implement such a functionality.

fyi. Dirty and temporary solution is to override console.warn with your own function :D

[TimothyGu]

Right now all errors are reported by console.warn function.

Huh? Only the warnings are reported by, well, warn(). Errors are/should be thrown right away.

[Martodox]

Yeah, thats correct.
But still, I'd like to break the build even if there are warnings in the code.
Having console.warn there in the code doesn't let me do that.

Don't you think that there should be some warn levels available?

• 0 - pass all
• 1 - warn only
• 2 - default (like it works right now)
• 3 - fail all (throws an error on every error or warning)