@ecency/sdk 2.3.14 → 2.3.16

package/dist/browser/index.d.ts

@@ -1,7 +1,7 @@
 import * as _tanstack_react_query from '@tanstack/react-query';
 import { MutationKey, UseMutationOptions, QueryClient, QueryKey, InfiniteData, UseQueryOptions, UseInfiniteQueryOptions, useMutation } from '@tanstack/react-query';
-import { O as Operation, R as PrivateKey, i as BroadcastResult, g as Authority, S as PublicKey, P as OperationName, aj as operations } from './hive-DfGQ3XAe.js';
-export { A as AccountCreateOperation, f as AssetSymbol, u as CustomJsonOperation, $ as HiveTxTransaction, M as Memo, N as OperationBody, _ as Signature, ae as callREST, af as callRPC, ag as callRPCBroadcast, ah as callWithQuorum, ai as hiveTxConfig, al as hiveTxUtils } from './hive-DfGQ3XAe.js';
+import { O as Operation, R as PrivateKey, i as BroadcastResult, g as Authority, S as PublicKey, P as OperationName, aj as operations } from './hive-fkgMnAQs.js';
+export { A as AccountCreateOperation, f as AssetSymbol, u as CustomJsonOperation, $ as HiveTxTransaction, M as Memo, N as OperationBody, _ as Signature, ae as callREST, af as callRPC, ag as callRPCBroadcast, ah as callWithQuorum, ai as hiveTxConfig, am as hiveTxUtils } from './hive-fkgMnAQs.js';
 
 interface AiGenerationPrice {
     aspect_ratio: string;
@@ -1015,6 +1015,14 @@ declare namespace ConfigManager {
      * @param nodes - Array of Hive RPC node URLs
      */
     function setHiveNodes(nodes: string[]): void;
+    /**
+     * Set the User-Agent sent on server-side (Node) requests to Hive nodes.
+     * Lets an app label its own SSR/server traffic (otherwise Node's fetch sends a
+     * bare `node` UA). No effect in browsers (User-Agent is a forbidden header) or
+     * React Native (keeps its native UA). Delegates to the unified hive-tx setter.
+     * @param userAgent - The User-Agent string (e.g. "ecency-web-ssr (+https://ecency.com)")
+     */
+    function setUserAgent(userAgent: string): void;
     /**
      * Set DMCA filtering lists
      * @param lists - DMCA lists object containing accounts/tags/posts arrays
@@ -4942,12 +4950,22 @@ interface UseStatsQueryOptions {
      * landed on it. The API route validates this against an allow-list.
      */
     filterBy?: "event:page" | "visit:entry_page";
+    /**
+     * Plausible `date_range`. Pass a tuple `[from, to]` (ISO `YYYY-MM-DD`) to scope
+     * the query — e.g. a post's creation date through today. Scoping is essential:
+     * ClickHouse orders events by `(site_id, toDate(timestamp), …)` and partitions
+     * by month, so a bounded range prunes to a few granules instead of scanning the
+     * whole history. Omitting it falls back to the route default (`"all"`), which on
+     * a high-traffic site is a multi-second full scan. Plausible also accepts the
+     * relative keywords `"day"`, `"7d"`, `"30d"`, `"all"`.
+     */
+    dateRange?: string | [string, string];
     enabled?: boolean;
 }
-declare function getStatsQueryOptions({ url, dimensions, metrics, filterBy, enabled, }: UseStatsQueryOptions): _tanstack_react_query.OmitKeyof<_tanstack_react_query.UseQueryOptions<StatsResponse, Error, StatsResponse, (string | string[])[]>, "queryFn"> & {
-    queryFn?: _tanstack_react_query.QueryFunction<StatsResponse, (string | string[])[], never> | undefined;
+declare function getStatsQueryOptions({ url, dimensions, metrics, filterBy, dateRange, enabled, }: UseStatsQueryOptions): _tanstack_react_query.OmitKeyof<_tanstack_react_query.UseQueryOptions<StatsResponse, Error, StatsResponse, (string | string[] | undefined)[]>, "queryFn"> & {
+    queryFn?: _tanstack_react_query.QueryFunction<StatsResponse, (string | string[] | undefined)[], never> | undefined;
 } & {
-    queryKey: (string | string[])[] & {
+    queryKey: (string | string[] | undefined)[] & {
         [dataTagSymbol]: StatsResponse;
         [dataTagErrorSymbol]: Error;
     };