You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the current architecture of the CLI, the error handling is often repeated and singular to each task. Updating any error messaging or handling can result in tedious work. The stack traces printed by unhandled errors can be intimidating and unhelpful to those that encounter them.
Using something like modern-errors, there could be custom errors for raising known issues and consolidated handlers higher up in the chain. Unknown error handling could also result in more helpful output, including a prompt to automatically create an issue in the xs-dev repo with the stack trace and any other environment info to help with debugging.
The text was updated successfully, but these errors were encountered:
In the current architecture of the CLI, the error handling is often repeated and singular to each task. Updating any error messaging or handling can result in tedious work. The stack traces printed by unhandled errors can be intimidating and unhelpful to those that encounter them.
Using something like modern-errors, there could be custom errors for raising known issues and consolidated handlers higher up in the chain. Unknown error handling could also result in more helpful output, including a prompt to automatically create an issue in the xs-dev repo with the stack trace and any other environment info to help with debugging.
The text was updated successfully, but these errors were encountered: