Repository navigation
Expand file tree
/
Copy pathindex.ts
More file actions
49 lines (46 loc) · 1.6 KB
/
Copy pathindex.ts
File metadata and controls
49 lines (46 loc) · 1.6 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
#!/usr/bin/env node
import chalk from 'chalk'
import { ProfileConfigError } from './config/index'
import {
formatApiErrorDetails,
isRequestTimeout,
RAISE_TIMEOUT_HINT,
SimApiError,
} from './http/client'
import { sanitize } from './output/render'
import { buildProgram } from './program'
/**
* Anything the CLI can explain prints as one line and exits 1. An unexpected
* error keeps its stack trace — that is a bug in the CLI, and hiding it behind a
* friendly message would make it unreportable.
*/
async function main() {
try {
await buildProgram().parseAsync(process.argv)
} catch (error) {
if (error instanceof ProfileConfigError) {
console.error(chalk.red(`Error: ${sanitize(error.message)}`))
process.exit(1)
}
// `AbortSignal.timeout` keeps firing after `fetch` resolves, so a bound that
// elapses while the body is still being read — a large `files get`, say —
// surfaces here rather than inside the client. A user's own Ctrl-C raises
// `AbortError` instead, which is deliberately left alone.
if (isRequestTimeout(error)) {
console.error(chalk.red(`Error: the request timed out. ${RAISE_TIMEOUT_HINT}`))
process.exit(1)
}
if (error instanceof SimApiError) {
console.error(chalk.red(`Error: ${sanitize(error.message)}`))
if (error.code) console.error(chalk.dim(` code: ${sanitize(error.code)}`))
if (error.details !== undefined) {
for (const line of formatApiErrorDetails(error.details)) {
console.error(chalk.dim(sanitize(line)))
}
}
process.exit(1)
}
throw error
}
}
main()