@fkn/lib 0.9.40 → 0.9.42

package/storage-ZrY4Y4L5.d.ts

@@ -1,88 +0,0 @@
-declare namespace storage_d_exports {
-  export { CloudAvailability, EncryptionStatus, FileEntry, SealedRead, StorageLockedError, StorageNotFoundError, StorageQuota, WriteData, availability, available, encryption, isNotFound, list, quota, readFile, readFileSealed, remove, unlock, writeFile };
-}
-type FileEntry = {
-  path: string;
-  size: number;
-  contentType: string | null;
-  updatedAt: string;
-  encryption: string | null;
-};
-type StorageQuota = {
-  usedBytes: number;
-  limitBytes: number;
-  remaining: number;
-  objects: number;
-  maxObjects: number;
-};
-type EncryptionStatus = {
-  unlocked: boolean;
-  enrolled: boolean;
-  keyEpoch: number | null;
-};
-type WriteData = Blob | ArrayBuffer | Uint8Array | string;
-declare class StorageLockedError extends Error {
-  code: string;
-  constructor();
-}
-/**
- * There is no object at this path. Test `err.code === STORAGE_NOT_FOUND`, never the message.
- *
- * Absence arrives from two places that word it completely differently: the api refusing to presign
- * a path with no committed row says "Not found", and a presign that succeeded followed by an object
- * fetch that 404s says "storage: read failed (404)". Neither is a fault, both mean the same thing,
- * and matching either by hand means matching both. Ripple matched only the first, so a missing
- * backup read as a transient failure, retried forever, and a library went un-backed-up for a day
- * without a single error anywhere.
- *
- * The distinction matters more than it sounds. "There is nothing here" is safe to overwrite;
- * "I could not tell you" is not, and a caller that confuses them either never writes a first
- * backup or destroys a real one.
- */
-declare class StorageNotFoundError extends Error {
-  code: string;
-  constructor(message?: string);
-}
-/** Whether an error from this module means the path is empty, as opposed to unreadable. */
-declare const isNotFound: (error: unknown) => boolean;
-declare const available: () => Promise<boolean>;
-type CloudAvailability = 'connected' | 'disconnected' | 'unknown';
-/**
- * Whether the cloud half is backed by an account, as three answers rather than two:
- * 'disconnected' is an ANSWER (signed out, or the api refusing the stored token), 'unknown'
- * means nobody could be asked, including a broker that never came up. Always settles within
- * the probe deadline. A caller owing data to the cloud may drop that obligation only on
- * 'disconnected'; treating 'unknown' the same silently loses the write.
- */
-declare const availability: () => Promise<CloudAvailability>;
-declare const list: () => Promise<FileEntry[]>;
-declare const quota: () => Promise<StorageQuota>;
-declare const readFile: (path: string) => Promise<Blob>;
-/** The bytes of a cloud object and the seal time they carry, as an ISO string or null. */
-type SealedRead = {
-  data: Uint8Array;
-  sealedAt: string | null;
-};
-/**
- * A cloud read that also reports when the copy was sealed.
- *
- * `sealedAt` is an ISO string, or null when the envelope carries no such field (one written before
- * the seal time existed) or when the data plane is older than this call. The value is
- * AUTHENTICATED, so the server can neither forge nor alter it, and it is the WRITER's own claim
- * about when it sealed, so on its own it does not prove this copy is the newest one: an older but
- * perfectly authentic copy of the same path is still authentic. An app that needs that answer keeps
- * a high-water mark per path and compares. Do not confuse it with the `updatedAt` on a listing,
- * which is the server's hint and is fine for display and nothing else.
- *
- * The bytes and the stamp come from ONE read of ONE envelope, which is what makes the stamp
- * describe the bytes returned beside it. `readFile` is unchanged and unaffected.
- */
-declare const readFileSealed: (path: string) => Promise<SealedRead>;
-declare const writeFile: (path: string, data: WriteData, opts?: {
-  contentType?: string;
-}) => Promise<void>;
-declare const remove: (path: string) => Promise<void>;
-declare const encryption: () => Promise<EncryptionStatus>;
-declare const unlock: () => Promise<boolean>;
-//#endregion
-export { StorageNotFoundError as a, isNotFound as c, storage_d_exports as d, unlock as f, StorageLockedError as i, quota as l, FileEntry as n, StorageQuota as o, SealedRead as r, encryption as s, EncryptionStatus as t, readFileSealed as u };