Is there a way to have an angular component throw an actually fatal error?

In our application, there are times when we the code isn't correct and we'd like to fail fast in that case. Say a component relies on a core configuration to function, but that configuration hasn't been defined for a particular use case. I'd like then to throw an error that would completely stop the Angular application, or at least that instance of the component. But when I try to do so, the error indeed appears, but is then obtructed in the log by a slew of subsequent obvious errors due to the missing config. Which shows that the component is still alive after the initial throw, which is what I'd like to avoid.

So how can I throw an error that actually stops the component (or the application)? What's the best practice for this?


One idea I have is to add a custom global error handler, and somehow tag errors that should be fatal so that our custom hanlder can detect them and let the app crash... But this seems like reinventing the wheel, to me it feels like what I'm asking for would be a workflow that Angular probably already handles.

Continue reading...