@zgeoff/imp-client 0.15.0 → 0.16.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +6 -5
- package/dist/index.d.ts +1542 -36
- package/dist/index.js +2 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -121,11 +121,12 @@ in a URL; a browser behind a proxy that adds the token works the same way.
|
|
|
121
121
|
|
|
122
122
|
`exit` resolves with `{ code, signal }`, where `code` is null when a signal ended the command. When
|
|
123
123
|
the command did not run to its exit, `exit` rejects with an `ExecError` whose `code` is impd's (as
|
|
124
|
-
in the table below, plus `EXEC_FAILED` when the command cannot start
|
|
125
|
-
for an exec ticket that expired or was used),
|
|
126
|
-
`
|
|
127
|
-
|
|
128
|
-
|
|
124
|
+
in the table below, plus `EXEC_FAILED` when the command cannot start and `INNER_DOWN` when the imp's
|
|
125
|
+
container is down) or one of `UNAUTHORIZED` (also for an exec ticket that expired or was used),
|
|
126
|
+
`UNREACHABLE`, `RESTARTING`, `CONNECTION_CLOSED`, `DETACHED`, `BAD_MESSAGE`, `CLOSED`,
|
|
127
|
+
`OUTPUT_OVERFLOW` and `LOCAL_ERROR`. Its `data` is impd's error data. An abort before the command
|
|
128
|
+
starts, during the ticket call or the connect, rejects with the abort's reason instead, an
|
|
129
|
+
`AbortError` by default; after the start it ends the session as `CLOSED`.
|
|
129
130
|
|
|
130
131
|
## Errors
|
|
131
132
|
|