naro-js 0.7.0 → 0.7.1

package/README.md

@@ -774,7 +774,10 @@ await naro.removeChannel(room);
   4003, 4004 and 4410 stop it — call `subscribe()` again; it connects after
   the backoff, counted from the stop, so a `subscribe()` in the
   `CHANNEL_ERROR` callback does not spin. 4029 comes back after 5 seconds at
-  least (60 to 70 for `IP_RATE_LIMITED`); 4503 after 0 to 10 seconds, every
+  least (60 to 70 for `IP_RATE_LIMITED`; 900 to 910 for
+  `REALTIME_QUOTA_EXCEEDED` — the project used its realtime messages for the
+  month (an operator's cap): tried again every 15 minutes, naro-js 0.7.1);
+  4503 after 0 to 10 seconds, every
   time; anything else after 1, 2, 5 and then 10 seconds, each times 0.5 to
   1.5 — after a 4008 the steps start over only once the connection outlived
   a heartbeat. Removing the last channel and subscribing again keeps the wait

package/dist/index.js

@@ -717,6 +717,9 @@ var RETRY_AFTER_CODES = /* @__PURE__ */ new Set([
   "STORAGE_OPS_QUOTA_EXCEEDED",
   // Realtime's REST broadcast over the project's message budget (x-retry-after: 1).
   "TOO_MANY_MESSAGES",
+  // The dispatcher's REST 429 of a project over its month of Realtime (3-2e):
+  // `x-retry-after` is the seconds to the 1st at 00:00 UTC.
+  "REALTIME_QUOTA_EXCEEDED",
   // Naro Functions (design F20): a team over its monthly function CPU, and
   // the control plane's Cloudflare limit. `invoke` reads x-retry-after on
   // every relay error anyway (invoke/client.ts).
@@ -2672,6 +2675,7 @@ var TableBuilder = class {
 var BACKOFF_STEPS_MS = [1e3, 2e3, 5e3, 1e4];
 var RATE_LIMITED_MIN_MS = 5e3;
 var IP_LIMIT_WAIT_MS = 6e4;
+var QUOTA_WAIT_MS = 9e5;
 var RESTART_JITTER_MS = 1e4;
 var UNOPENED_SLOWDOWN_AFTER = 6;
 var UNOPENED_DELAY_MS = 6e4;
@@ -2688,7 +2692,7 @@ function closeAction(code, reason) {
   if (code === 4401) return { kind: "session" };
   if (code === 4503) return { kind: "restart" };
   if (code === 4029)
-    return reason === "IP_RATE_LIMITED" ? { kind: "wait", ms: IP_LIMIT_WAIT_MS } : { kind: "retry", minMs: RATE_LIMITED_MIN_MS };
+    return reason === "IP_RATE_LIMITED" ? { kind: "wait", ms: IP_LIMIT_WAIT_MS } : reason === "REALTIME_QUOTA_EXCEEDED" ? { kind: "wait", ms: QUOTA_WAIT_MS } : { kind: "retry", minMs: RATE_LIMITED_MIN_MS };
   return { kind: "retry", minMs: 0 };
 }
 function backoffMs(attempt2, random) {

package/dist/realtime/close.d.ts

@@ -4,6 +4,12 @@ export declare const BACKOFF_STEPS_MS: readonly [1000, 2000, 5000, 10000];
 export declare const RATE_LIMITED_MIN_MS = 5000;
 /** The dispatcher's per-address window is a fixed minute (3-2c-2 결정 9). */
 export declare const IP_LIMIT_WAIT_MS = 60000;
+/**
+ * A month's block (Realtime 3-2e): the meter looks again every 15 minutes, so
+ * a refused client comes back on that beat — not every few seconds for the
+ * rest of the month. After the 1st it is back within about 15 minutes.
+ */
+export declare const QUOTA_WAIT_MS = 900000;
 /**
  * A restart closes everyone at once, so every 4503 return waits 0–10 s (design
  * D6). The wait does not grow with the attempt count or the unopened tries:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "naro-js",
-  "version": "0.7.0",
+  "version": "0.7.1",
   "description": "Auth, data and files for your Naro project, from the browser or the server.",
   "type": "module",
   "sideEffects": false,
@@ -34,11 +34,11 @@
     "tsup": "8.5.0",
     "typescript": "7.0.2",
     "vitest": "3.2.7",
+    "@next-deploy/backend-worker": "0.1.0",
     "@next-deploy/config": "0.1.0",
-    "@next-deploy/data-core": "0.1.0",
-    "@next-deploy/sdk": "0.1.0",
     "@next-deploy/functions-runtime": "0.1.0",
-    "@next-deploy/backend-worker": "0.1.0"
+    "@next-deploy/sdk": "0.1.0",
+    "@next-deploy/data-core": "0.1.0"
   },
   "scripts": {
     "build": "tsup && pnpm build:types",