Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Investigate ways to allow devs to handle fatal load errors #42

Open
unscriptable opened this issue Jun 17, 2014 · 2 comments
Open

Investigate ways to allow devs to handle fatal load errors #42

unscriptable opened this issue Jun 17, 2014 · 2 comments

Comments

@unscriptable
Copy link
Contributor

At the moment, there's no prescriptive way to catch fatal loading errors. Devs should be able to hook into an event or override a method to do something sane and/or helpful for their users, such as display a friendly error page.

@pocesar
Copy link

pocesar commented Jun 18, 2014

https://www.npmjs.org/package/trycatch? or it needs a browser equivalent version?

@unscriptable
Copy link
Contributor Author

Hey @pocesar! Thanks for the link. That's a useful library. Async exceptions are nasty to wrangle. Ask @briancavalier who figured out how to wrangle them in when.js. :)

Actually, what I am asking is a bit different. What is the best mechanism to allow an application developer to listen for fatal events that happen in rave. Rave can already catch and handle almost everything (And will handle everything the next time we update the ES6 Loader shim). We just need to figure out the best API for application devs. Any ideas?

@unscriptable unscriptable changed the title Investigate ways to allow devs to catch fatal load errors Investigate ways to allow devs to handle fatal load errors Jun 25, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants