[feature request] build chain error handling

_From @wzr1337 on June 28, 2016 21:49_

I just had an issue with code that did not compile because I wanted to assign a number to a string. Typescript did not compile. This caused to browser code I was running to remain the same. Unfortunately, I did not notice the error in the shell, because it was hidden behind the editor.

I would strongly recommend to catch any build error, pipe it into a static page and refresh the app in the browser with just the error page. This way, developers will be immediately aware of errors, that prevent code from being actually build and refreshed in the browser. Angular.cli for examples does catch all kinds of errors and puts them on the error age they show instead of the app in case of any errors.

The errors to catch would be any kind of .ts and *.scss and so on.

Best regards

_Copied from original issue: driftyco/ionic#7105_

Start by tracing how the Ionic CLI reports TypeScript and SCSS build errors and how it refreshes browser output. Compare the requested behavior with the Angular CLI example mentioned in the issue; done should mean build failures are surfaced in a browser error page instead of leaving the previous app running.

Escrita pelo modelo de indexação a partir do texto da issue.