Errors must be communicated through appropriate mechanisms for their execution context. In CLI applications, use proper exit codes to indicate error states (non-zero for failures). For shell command execution, implement proper error handling to prevent unexpected crashes and provide graceful failure modes.
For CLI tools, always set appropriate exit codes when errors occur:
if (err) {
spinner.stop("Upgrade failed", 1) // Exit code 1 for error
// ... handle error logging
}
For shell commands, use error handling mechanisms like .quiet().nothrow() to prevent crashes:
await $`curl -L -o '${archivePath}' '${releaseURL}'`.quiet().nothrow()
await $`tar -xzf ${archivePath}`.cwd(distPath).quiet().nothrow()
This ensures that errors are properly signaled to the appropriate layer (operating system, calling process, or user interface) and prevents silent failures or unexpected crashes.
Enter the URL of a public GitHub repository