@dskripchenko/laravel-admin 1.44.1 → 1.45.1

package/dist/.vite/manifest.json

@@ -1,11 +1,11 @@
 {
   "resources/ts/app.ts": {
-    "file": "assets/app-BSLBKVsR.js",
+    "file": "assets/app-B4vfwKxh.js",
     "name": "app",
     "src": "resources/ts/app.ts",
     "isEntry": true,
     "css": [
-      "assets/app-D8xmSFFQ.css"
+      "assets/app-D1N69Xpm.css"
     ]
   }
 }

package/dist/api/errors.d.ts

@@ -38,3 +38,17 @@ export declare class NetworkError extends Error {
  * Turns an HTTP status and an envelope into the right ApiError subclass.
  */
 export declare function toApiError(status: number, payload: ErrorEnvelope['payload']): ApiError;
+/**
+ * The reason the server gave for refusing a request, or `fallback` when it
+ * gave none.
+ *
+ * A validation error answers with its first field message (the envelope's own
+ * message is usually a generic "The given data was invalid"), then the
+ * envelope's message — which is what an `action_failed` 422 carries. Any
+ * other ApiError answers with the envelope's message: a 403 says which
+ * permission is missing. A response with no envelope at all (see the
+ * client's `transport` marker) and the synthetic "API error 500" the ApiError
+ * constructor falls back to are not reasons, so they yield `fallback`. Plain
+ * errors (a network failure, a client-side check) answer with their message.
+ */
+export declare function apiErrorMessage(err: unknown, fallback: string): string;