@tinycloud/cli 1.3.0-beta.33 → 1.3.0-beta.35

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.
Files changed (6) hide show
  1. package/dist/index.js +220 -132
  2. package/dist/index.js.map +1 -1
  3. package/dist/legacy-entry.js +212 -145
  4. package/dist/legacy-entry.js.map +1 -1
  5. package/package.json +6 -6
  6. package/skills/tc-cli/REFERENCE.md +4 -0
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@tinycloud/cli",
3
- "version": "1.3.0-beta.33",
3
+ "version": "1.3.0-beta.35",
4
4
  "description": "TinyCloud CLI - manage data, delegations, and nodes from the terminal",
5
5
  "author": "TinyCloud, Inc.",
6
6
  "license": "EGPL",
@@ -35,11 +35,11 @@
35
35
  "dependencies": {
36
36
  "@tinycloud/share-sdk": "1.2.0-beta.6",
37
37
  "@tinycloud/share-envelope": "1.2.0-beta.0",
38
- "@tinycloud/node-sdk": "3.3.0-beta.30",
39
- "@tinycloud/node-sdk-wasm": "1.7.7",
40
- "@tinycloud/sdk-core": "3.3.0-beta.30",
38
+ "@tinycloud/node-sdk": "3.3.0-beta.31",
39
+ "@tinycloud/node-sdk-wasm": "1.7.8-beta.0",
40
+ "@tinycloud/sdk-core": "3.3.0-beta.31",
41
41
  "@tinycloud/sdk-services": "3.3.0-beta.25",
42
- "@tinycloud/operations": "0.6.1-beta.28",
42
+ "@tinycloud/operations": "0.6.1-beta.29",
43
43
  "chalk": "^5.3.0",
44
44
  "commander": "^14.0.0",
45
45
  "open": "^11.0.0",
@@ -47,7 +47,7 @@
47
47
  "siwe": "^3.0.0"
48
48
  },
49
49
  "devDependencies": {
50
- "@tinycloud/courier": "0.1.6-beta.28",
50
+ "@tinycloud/courier": "0.1.6-beta.29",
51
51
  "@tinycloud/replica": "0.3.0-beta.8",
52
52
  "@types/node": "^20",
53
53
  "tsup": "^8.0.0",
package/skills/tc-cli/REFERENCE.md CHANGED
@@ -396,6 +396,10 @@ The fragment after `#` is the read key. Browsers never send it to a server; `--n
396
396
 
397
397
  Share publication without `--expires` requests a seven-day lifetime. For a session-only profile, the CLI clamps that request to the verified SIWE session expiry, prints a notice to stderr, and reports `"expiryClamped": true` in JSON. Explicit lifetimes beyond the session end, or with less than 60 seconds left after second-precision rounding, fail with `SESSION_LIFETIME_EXCEEDED`. Expired/invalid restored sessions and missing owner authority return `AUTH_REQUIRED`; rejected KV upload or delegation scopes return `PERMISSION_DENIED`. A session-only profile whose authority for an anyone-with-link share carries signed restrictions (caveats) is refused with `PERMISSION_DENIED` before anything is stored, because the link's delegation cannot carry the caveats; approve Share publishing without restrictions on a new profile (`tinycloud init --name publisher --key-only && tinycloud --profile publisher enable share`). Full TinyCloud storage returns the general storage-full error (`STORAGE_QUOTA_EXCEEDED` or `STORAGE_LIMIT_REACHED`, exit 10), and any other failed upload returns `UPLOAD_FAILED`; nothing is shared in either case. A filename that has characters other than `A-Z a-z 0-9 . _ -`, starts with anything but a letter or digit, contains `..`, or is longer than 128 characters is stored under a readable URI-safe name. It keeps its extension when that is 1-16 ASCII letters or digits (`Q3 plan (draft).md` is stored as `Q3-plan-draft.md`, `.env` as `share.env`); otherwise its dots become dashes, so it never gains one. Bearer links show the stored name and `receive` writes it, while addressed links keep the original. JSON publish output includes `expiryClamped: false` when no clamp was needed.
398
398
 
399
+ **`SPACE_NOT_READY`** (exit 4). A share upload the node answered with `404 Space not found` for the owner space. A node restart can leave an empty space unregistered until it is first written; the node fix (1.21.5) is pending. Nothing sets the space up from the client, so retries keep failing until the node is updated: retry after the node update, and contact support with the code if it persists. Nothing was shared and repeating the command is safe. Only this write-time 404 maps here; other 404s (an unknown share, a missing key on a read) keep their own errors. The node's error is kept as the error's `cause`, not printed.
400
+
401
+ A node or network failure that no specific Share mapping claims is named by class and HTTP status rather than `INVALID_ARGUMENT`: `AUTH_REQUIRED` (401, exit 3), `PERMISSION_DENIED` (403, exit 5), `NOT_FOUND` (404, exit 4), `NODE_UNAVAILABLE` (5xx/408/429, exit 7), `NETWORK_ERROR` (node unreachable, exit 6), `INVALID_ARGUMENT` (400/422, exit 2) and `NODE_REJECTED` (other 4xx, exit 1). The message carries fixed wording plus the status and a plain upstream code (`HTTP 502, UPSTREAM_DOWN`), never the node's response text; an error with no such signal still reports `share operation failed`.
402
+
399
403
  ### Share Publish Options
400
404
 
401
405
  | Flag | Description | Default |