narraleaf-react 0.41.1 → 0.42.0

package/dist/util/data.d.ts

@@ -245,7 +245,21 @@ export type ExcludeEach<T extends string[][], Excluded> = T extends [infer First
 export type FlexibleTuple<T extends any[]> = T extends [infer First, ...infer Rest] ? Rest extends any[] ? [First, ...FlexibleTuple<Rest>] | FlexibleTuple<Rest> : [First] : [];
 export declare function moveElement<T>(arr: T[], element: T, direction: "up" | "down" | "top" | "bottom"): T[];
 export declare function moveElementInArray<T>(arr: T[], element: T, newIndex: number): T[];
-export declare function getImageDataUrl(src: string, options?: RequestInit): Promise<string>;
+/**
+ * Fetch `src` and hand back a URL for the same bytes that an `<img>` can be pointed at.
+ *
+ * An object URL rather than a data URL, which is what this used to produce. A data URL costs a
+ * base64 encode of the whole file (about a third larger than the bytes), keeps that string alive
+ * for as long as the cache holds the entry, and makes the browser decode the base64 back to bytes
+ * before it can decode the image. An object URL is a handle to the blob that is already in memory:
+ * no encode, no string, and the decode reads the bytes directly. Measured over a 241 MB image
+ * library, the whole fetch-and-decode pass drops by about a third.
+ *
+ * The caller owns the URL and MUST call {@link URL.revokeObjectURL} when it stops using it -
+ * an object URL pins its blob for the lifetime of the document otherwise. {@link ImageCacheManager}
+ * is the only caller and revokes on every path that drops an entry.
+ */
+export declare function getImageObjectUrl(src: string, options?: RequestInit): Promise<string>;
 export declare class TaskPool {
     private readonly concurrency;
     private readonly delay;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "narraleaf-react",
-  "version": "0.41.1",
+  "version": "0.42.0",
   "description": "A React visual novel player framework",
   "type": "module",
   "main": "./dist/main.js",