feat: add partial (batched) deployment support

.vscode/settings.json

@@ -14,8 +14,8 @@
     120
   ],
   "editor.codeActionsOnSave": {
-    "source.fixAll.eslint": true,
-    "source.organizeImports": true
+    "source.fixAll.eslint": "explicit",
+    "source.organizeImports": "explicit"
   },
   "eslint.validate": [
     "typescript"

README.md

@@ -15,3 +15,36 @@ npm install dcl-catalyst-client
 ### Examples
 
 Please check the [examples repository](https://github.com/decentraland/catalyst-client-examples)
+
+### Partial (batched) deployments
+
+For entities too large to upload in a single request, use `deployPartial`. It splits the content into
+size-bounded batches and uploads them across several `POST /entities` requests; the entity only becomes
+live once the server has all of it (the server finalizes automatically on the completing request).
+
+```ts
+const result = await client.deployPartial(
+  { entityId, authChain, files },
+  {
+    // default: 100 MiB per request — requests larger than ~200MB are timed out by the
+    // infrastructure in front of the content servers, so keep a margin under that.
+    maxBatchSizeBytes: 100 * 1024 * 1024,
+    concurrency: 2, // default: 2 parallel batch uploads (after the first)
+    maxResumeAttempts: 3, // default: 3 — resumes on network/5xx failures
+    onProgress: ({ uploadedBytes, totalBytes }) => console.log(`${uploadedBytes}/${totalBytes}`)
+  }
+)
+console.log(result.creationTimestamp)
+```
+
+Notes:
+
+- The regular `deploy()` is unchanged; use it for normal-sized deployments.
+- The target server must support partial deployments. Against an older server that does not, a
+  single-batch deployment still succeeds, but a multi-batch one rejects with
+  `PartialDeploymentNotSupportedError` — fall back to `deploy()` in that case.
+- A validation failure on the finalizing request (e.g. exceeding the size budget) rejects with
+  `PartialDeploymentValidationError`.
+- Files are never split across requests: a single file larger than the batch cap is sent alone in its
+  own request. Per-file server caps still apply to it, and a request beyond ~200MB may be timed out by
+  the infrastructure regardless of the configured cap.