When navigating to the error page on API failures, no error context is passed. Consider passing error details via navigation state (e.g., navigate('/error', { state: { error: error.message } })) so that the error page can display more helpful information to users and aid in debugging. This would be particularly helpful for distinguishing between different types of failures (network issues, server errors, etc.).
Originally posted by @Copilot in #3 (comment)