[UIX CLI] Error Handling Collection Issue

[asbng]

Acknowledgement

• This issue is not a bug report or feature request. I acknowledge that issues using this template may be closed without further explanation at the maintainer's discretion.

Comment

This post shall serve as a collection of issues related to the stability of the UIX Command Line Interface (run.ts).

Issues

• Catch error when trying to delete non-existing deno.lock file #143
• [Uncaught Promise] uix --init: Failed to clone #145
• [Uncaught Promise] uix --init: ENOENT when git is not installed #146
• [Uncaught Promise] UIX CLI: DNS error when offline #147

General Guidelines

• As UIX strives to offer a good experience to professional and novice developers alike, error messages MUST be clear and concise.
• As JavaScript errors are polluted with internal code information and don't necessarily carry descriptive error messages, those errors MUST NOT be shown to the user.
• Errors SHOULD be prevented (for instance, by performing preconditional checks) but MAY be handled with try {} catch {} instead.
• Errors SHOULD be recovered by fallback action. If this is not possible, clear and concise error or warning messages MUST be printed.
• All code pieces that may potentially raise I/O (network, filesystem, command execution) errors MUST be handled.