@cosmicdrift/kumiko-dispatcher-live 0.337.1 → 0.338.0

package/dist/dispatcher-live.js

@@ -155,10 +155,7 @@ export function createLiveDispatcher(options = {}) {
                 }
                 const body = parsed;
                 if (body?.error) {
-                    throw mapServerError({
-                        ...body.error,
-                        httpStatus: body.error.httpStatus ?? response.status,
-                    });
+                    throw mapServerErrorWithStatus(body.error, response.status);
                 }
                 throw buildNetworkError(`unexpected non-SSE stream response (${response.status})`);
             }
@@ -208,7 +205,7 @@ function normalizeWriteResult(call) {
     const body = call.body;
     if (body.isSuccess)
         return body;
-    return { isSuccess: false, error: mapServerError(body.error) };
+    return { isSuccess: false, error: mapServerErrorWithStatus(body.error, call.status) };
 }
 function normalizeBatchResponse(call) {
     if (!call.ok) {
@@ -219,7 +216,7 @@ function normalizeBatchResponse(call) {
         return body;
     return {
         isSuccess: false,
-        error: mapServerError(body.error),
+        error: mapServerErrorWithStatus(body.error, call.status),
         failedIndex: body.failedIndex,
         results: body.results,
     };
@@ -228,23 +225,22 @@ function normalizeBatchResponse(call) {
 // (no isSuccess flag) and `{ error: { code, i18nKey, message, ... } }`
 // on failure. Source of truth: packages/framework/src/api/routes.ts:85
 // (the query route handler that emits `c.json({ data: result })`).
-// The HTTP status carries the failure-status; the error body itself
-// doesn't repeat it (serializeError drops httpStatus to keep the wire
-// payload lean). We have to reinject httpStatus from the Response.status
-// here.
 function normalizeQueryResponse(call) {
     if (!call.ok)
         return { isSuccess: false, error: call.networkFailure };
     const body = call.body;
     if (body && "error" in body && body.error) {
-        const errorWithStatus = {
-            ...body.error,
-            httpStatus: body.error.httpStatus ?? call.status,
-        };
-        return { isSuccess: false, error: mapServerError(errorWithStatus) };
+        return { isSuccess: false, error: mapServerErrorWithStatus(body.error, call.status) };
     }
     return { isSuccess: true, data: body?.data };
 }
+// The HTTP status carries the failure-status; the error body itself
+// doesn't repeat it (serializeError drops httpStatus to keep the wire
+// payload lean). Every envelope has to reinject it from Response.status,
+// otherwise status-based checks like isSessionEndedError never match.
+function mapServerErrorWithStatus(error, responseStatus) {
+    return mapServerError({ ...error, httpStatus: error.httpStatus ?? responseStatus });
+}
 function isAbortError(e) {
     return (!!e &&
         typeof e === "object" &&

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@cosmicdrift/kumiko-dispatcher-live",
-  "version": "0.337.1",
+  "version": "0.338.0",
   "description": "HTTP-only Dispatcher for Kumiko UIs. Always-online; failures surface immediately. Default client for web admin/cockpit apps.",
   "license": "BUSL-1.1",
   "author": "Marc Frost <marc@cosmicdriftgamestudio.com>",
@@ -24,7 +24,7 @@
     }
   },
   "dependencies": {
-    "@cosmicdrift/kumiko-headless": "0.337.1"
+    "@cosmicdrift/kumiko-headless": "0.338.0"
   },
   "publishConfig": {
     "registry": "https://registry.npmjs.org",

package/src/changes.json

@@ -0,0 +1,8 @@
+[
+  {
+    "version": "0.338.0",
+    "type": "fix",
+    "title": "Write and batch errors carry httpStatus from the response",
+    "detail": "dispatcher-live: write and batch failures now take `httpStatus` from the HTTP response when the server's error body omits it, like queries already did. `isSessionEndedError` now also triggers on a failed write after the session ended."
+  }
+]