@fkn/lib 0.9.43 → 0.9.44

package/messages-CRcziTuC.d.ts

@@ -1,46 +0,0 @@
-//#region src/messages.d.ts
-declare const E2E_LOCKED_MESSAGE = "fkn:e2e-locked";
-declare const E2E_STALE_EPOCH_MESSAGE = "fkn:e2e-stale-epoch: this file is encrypted under a previous key you reset";
-declare const E2E_INTEGRITY_MESSAGE = "fkn:e2e-integrity: stored data failed its integrity check";
-/** the row is sealed in a format this version no longer opens (an envelope older than v3); distinct from integrity, since the bytes are intact */
-declare const E2E_RETIRED_FORMAT_MESSAGE = "fkn:e2e-retired-format: stored data is in a format this version no longer opens";
-/**
- * "There is no object at this path", as a thing a caller can TEST rather than parse.
- *
- * osra's error boxer ships name, message, stack and cause ONLY, so this code survives same-realm
- * hops but NOT the SharedWorker boundary; the message fallback in src/lib/storage.ts's rethrow is
- * what carries absence across that hop and re-mints the coded error for apps. The message does not
- * survive being reworded, which is the problem this exists to end: absence arrives in two
- * completely different sentences depending on which half of the read failed, and every consumer
- * was left regex-matching both. Ripple got one of them and missed the other, and a library quietly
- * went un-backed-up for a day because a missing backup read as a transient error.
- */
-declare const STORAGE_NOT_FOUND = "FKN_STORAGE_NOT_FOUND";
-/**
- * "The api never answered", as a thing a caller can TEST, for the same reason as above and one
- * more: a caller that relaxes anything when the server cannot be reached must never relax it on
- * an ANSWERED error, because an answered 500 lands exactly when a key rotation or a setting flip
- * may be propagating. The MESSAGE prefix is the wire contract: osra's error boxer ships name,
- * message, stack and cause only, so a custom code does NOT survive the SharedWorker hop (the
- * E2E_LOCKED_MESSAGE prefix match exists for exactly this reason). The code is still set for
- * same-realm callers, which is the cheaper test when it is available.
- */
-declare const STORAGE_UNREACHABLE = "FKN_API_UNREACHABLE";
-/**
- * The account pin's refusals, as message prefixes the broker throws, for the same reason as the e2e
- * messages above: osra keeps an Error's message and strips its code across the SharedWorker hop.
- *
- * `ACCOUNT_CHANGED_MESSAGE`: the api refused a call because the signed-in account is not the one its
- * pin was taken under. `ACCOUNT_PIN_INVALID_MESSAGE`: the api could not read the pin at all.
- * `ACCOUNT_PIN_UNSUPPORTED_MESSAGE`: some hop (the broker document or its shared worker) is older than
- * the pin, so the call was refused rather than sent unpinned. None of the three is a sign-out.
- */
-declare const ACCOUNT_CHANGED_MESSAGE = "fkn:account-changed";
-declare const ACCOUNT_PIN_INVALID_MESSAGE = "fkn:account-pin-invalid";
-declare const ACCOUNT_PIN_UNSUPPORTED_MESSAGE = "fkn:account-pin-unsupported";
-/** The code of `StorageAccountChangedError`: a call made under one account was refused under another. */
-declare const STORAGE_ACCOUNT_CHANGED = "FKN_ACCOUNT_CHANGED";
-/** The code of `StorageAccountPinUnsupportedError`: the broker cannot pin calls, so none was sent. */
-declare const STORAGE_ACCOUNT_PIN_UNSUPPORTED = "FKN_ACCOUNT_PIN_UNSUPPORTED";
-//#endregion
-export { E2E_LOCKED_MESSAGE as a, STORAGE_ACCOUNT_CHANGED as c, STORAGE_UNREACHABLE as d, E2E_INTEGRITY_MESSAGE as i, STORAGE_ACCOUNT_PIN_UNSUPPORTED as l, ACCOUNT_PIN_INVALID_MESSAGE as n, E2E_RETIRED_FORMAT_MESSAGE as o, ACCOUNT_PIN_UNSUPPORTED_MESSAGE as r, E2E_STALE_EPOCH_MESSAGE as s, ACCOUNT_CHANGED_MESSAGE as t, STORAGE_NOT_FOUND as u };