An unhandled error could pause execution, causing users to needlessly wait bewildered. A visible error may prompt them to
refresh the page, report the bug or open the dev console.
You might've forgotten to implement a specific error handler, included the wrong script, had network issues, etc.
You won't get the stack trace but you'll instantly know to look at the console. During development I sometimes stare at a
page wondering why something isn't happening. An error toast removes the wait and I immediately start debugging.
If you want to track your errors on a dashboard, which is the right thing to do if you have a site with a lot of visitors,
I'm told
rollbar works well and I've enjoyed using
Google's Stackdriver JS Error Reporting. Though it still might make sense to toast.
Because you need to paste it first into your `head` tag. I'm not sure how to arrange for that with webpack and other build
systems, PRs would be welcome.