Overview
This chapter is the fourth category, following "Optimization," "Testing," and "Store Design."
Async Errors and Store-Level Error State
A Store method that performs an async operation — an API call, a file read, anything that can fail — should not let an exception simply propagate up and out to whatever called it. If a component calls store.fetchUser() inside a click handler and that promise rejects, the rejection has nowhere meaningful to go; nothing in the template is listening for it, and it ends up as an unhandled rejection in the console at best.
Errors in Lifecycle Hooks
geajs has no equivalent of React's error boundaries. Nothing in the framework catches an exception thrown from created() or onAfterRender() and swaps in a fallback UI. What actually happens is worse than "that one component fails to render" — it's worth understanding precisely, because the failure mode is more severe than it looks at first glance.