@lunora/react-native 1.0.0-alpha.3 → 1.0.0-alpha.5

package/dist/auth.d.mts

@@ -1,35 +1,35 @@
 export { expoClient, setupExpoFocusManager, setupExpoOnlineManager } from '@better-auth/expo/client';
 /**
-* Read the current better-auth session token from an Expo auth client, for use
-* as a **bearer** credential on the Lunora client — `client.setAuthToken(token)`
-* for HTTP RPC and `client.setWsToken(token ?? undefined)` for the live socket.
-*
-* The Expo plugin persists the session as a cookie in `SecureStore`;
-* `getCookie()` exposes it, and this pulls the `session_token` value out.
-* better-auth's `bearer` plugin accepts that value verbatim in the
-* `Authorization` header — so the native client authenticates WITHOUT sending a
-* `Cookie`, which the runtime's CSRF guard rejects on an `Origin`-less native
-* request (React Native sends no `Origin`). Returns `null` when signed out.
-*
-* Re-run it whenever the session changes and feed the result to the client (see
-* the package README):
-*
-* ```ts
-* const token = expoBearerToken(authClient);
-* client.setAuthToken(token);
-* client.setWsToken(token ?? undefined);
-* ```
-* @experimental
-*/
+ * Read the current better-auth session token from an Expo auth client, for use
+ * as a **bearer** credential on the Lunora client — `client.setAuthToken(token)`
+ * for HTTP RPC and `client.setWsToken(token ?? undefined)` for the live socket.
+ *
+ * The Expo plugin persists the session as a cookie in `SecureStore`;
+ * `getCookie()` exposes it, and this pulls the `session_token` value out.
+ * better-auth's `bearer` plugin accepts that value verbatim in the
+ * `Authorization` header — so the native client authenticates WITHOUT sending a
+ * `Cookie`, which the runtime's CSRF guard rejects on an `Origin`-less native
+ * request (React Native sends no `Origin`). Returns `null` when signed out.
+ *
+ * Re-run it whenever the session changes and feed the result to the client (see
+ * the package README):
+ *
+ * ```ts
+ * const token = expoBearerToken(authClient);
+ * client.setAuthToken(token);
+ * client.setWsToken(token ?? undefined);
+ * ```
+ * @experimental
+ */
 declare const expoBearerToken: (authClient: {
   getCookie: () => string;
 }) => null | string;
 /**
-* The slice of a key/value store the better-auth Expo plugin needs — the shape
-* of `expo-secure-store` (a synchronous `getItem`, plus `setItem`). Pass Expo
-* `SecureStore` straight in.
-* @experimental
-*/
+ * The slice of a key/value store the better-auth Expo plugin needs — the shape
+ * of `expo-secure-store` (a synchronous `getItem`, plus `setItem`). Pass Expo
+ * `SecureStore` straight in.
+ * @experimental
+ */
 interface SecureStorageLike {
   getItem: (key: string) => null | string;
   setItem: (key: string, value: string) => unknown;

package/dist/auth.d.ts

@@ -1,35 +1,35 @@
 export { expoClient, setupExpoFocusManager, setupExpoOnlineManager } from '@better-auth/expo/client';
 /**
-* Read the current better-auth session token from an Expo auth client, for use
-* as a **bearer** credential on the Lunora client — `client.setAuthToken(token)`
-* for HTTP RPC and `client.setWsToken(token ?? undefined)` for the live socket.
-*
-* The Expo plugin persists the session as a cookie in `SecureStore`;
-* `getCookie()` exposes it, and this pulls the `session_token` value out.
-* better-auth's `bearer` plugin accepts that value verbatim in the
-* `Authorization` header — so the native client authenticates WITHOUT sending a
-* `Cookie`, which the runtime's CSRF guard rejects on an `Origin`-less native
-* request (React Native sends no `Origin`). Returns `null` when signed out.
-*
-* Re-run it whenever the session changes and feed the result to the client (see
-* the package README):
-*
-* ```ts
-* const token = expoBearerToken(authClient);
-* client.setAuthToken(token);
-* client.setWsToken(token ?? undefined);
-* ```
-* @experimental
-*/
+ * Read the current better-auth session token from an Expo auth client, for use
+ * as a **bearer** credential on the Lunora client — `client.setAuthToken(token)`
+ * for HTTP RPC and `client.setWsToken(token ?? undefined)` for the live socket.
+ *
+ * The Expo plugin persists the session as a cookie in `SecureStore`;
+ * `getCookie()` exposes it, and this pulls the `session_token` value out.
+ * better-auth's `bearer` plugin accepts that value verbatim in the
+ * `Authorization` header — so the native client authenticates WITHOUT sending a
+ * `Cookie`, which the runtime's CSRF guard rejects on an `Origin`-less native
+ * request (React Native sends no `Origin`). Returns `null` when signed out.
+ *
+ * Re-run it whenever the session changes and feed the result to the client (see
+ * the package README):
+ *
+ * ```ts
+ * const token = expoBearerToken(authClient);
+ * client.setAuthToken(token);
+ * client.setWsToken(token ?? undefined);
+ * ```
+ * @experimental
+ */
 declare const expoBearerToken: (authClient: {
   getCookie: () => string;
 }) => null | string;
 /**
-* The slice of a key/value store the better-auth Expo plugin needs — the shape
-* of `expo-secure-store` (a synchronous `getItem`, plus `setItem`). Pass Expo
-* `SecureStore` straight in.
-* @experimental
-*/
+ * The slice of a key/value store the better-auth Expo plugin needs — the shape
+ * of `expo-secure-store` (a synchronous `getItem`, plus `setItem`). Pass Expo
+ * `SecureStore` straight in.
+ * @experimental
+ */
 interface SecureStorageLike {
   getItem: (key: string) => null | string;
   setItem: (key: string, value: string) => unknown;

package/dist/index.d.mts

@@ -1,78 +1,78 @@
 import { AsyncStorageLike, LunoraClientOptions, LunoraClient } from '@lunora/client';
 export * from '@lunora/react';
 /**
-* A `() => headers` factory the React Native client threads onto every HTTP RPC
-* request *and* the WebSocket upgrade — a generic escape hatch for attaching a
-* **custom** credential header (an API-gateway key, a proxy token, …) that
-* React Native's missing cookie jar can't carry implicitly. Return `undefined`
-* (or an empty object) when there's nothing to attach.
-*
-* For better-auth Expo sessions, prefer a **bearer** token instead: read it with
-* `@lunora/react-native/auth`'s `expoBearerToken` and feed it to
-* `client.setAuthToken` / `setWsToken` (see the package README). A bearer avoids
-* the `Cookie` header the runtime's CSRF guard rejects on `Origin`-less native
-* requests.
-* @experimental
-*/
+ * A `() => headers` factory the React Native client threads onto every HTTP RPC
+ * request *and* the WebSocket upgrade — a generic escape hatch for attaching a
+ * **custom** credential header (an API-gateway key, a proxy token, …) that
+ * React Native's missing cookie jar can't carry implicitly. Return `undefined`
+ * (or an empty object) when there's nothing to attach.
+ *
+ * For better-auth Expo sessions, prefer a **bearer** token instead: read it with
+ * `@lunora/react-native/auth`'s `expoBearerToken` and feed it to
+ * `client.setAuthToken` / `setWsToken` (see the package README). A bearer avoids
+ * the `Cookie` header the runtime's CSRF guard rejects on `Origin`-less native
+ * requests.
+ * @experimental
+ */
 type AuthHeadersFactory = () => Record<string, string> | undefined;
 /**
-* Options for `createLunoraClient` — the React Native / Expo counterpart to
-* constructing a `LunoraClient` directly. It is `LunoraClientOptions` with two
-* React-Native-shaped conveniences layered on. `storage` wires the
-* AsyncStorage-backed offline-queue persistence for you (the browser default
-* auto-probes IndexedDB, which React Native lacks, so without this the queue
-* stays in memory and is lost on reload). `getAuthHeaders` is a generic escape
-* hatch for a custom credential header on both the HTTP RPC path and the
-* WebSocket upgrade; for better-auth sessions prefer a bearer token
-* (`expoBearerToken` + the client's `setAuthToken` / `setWsToken`).
-*
-* The `persistence`, `fetch`, and `WebSocket` fields of `LunoraClientOptions`
-* are still accepted and take precedence when you need full control; the two
-* conveniences are sugar over exactly those seams.
-* @experimental
-*/
+ * Options for `createLunoraClient` — the React Native / Expo counterpart to
+ * constructing a `LunoraClient` directly. It is `LunoraClientOptions` with two
+ * React-Native-shaped conveniences layered on. `storage` wires the
+ * AsyncStorage-backed offline-queue persistence for you (the browser default
+ * auto-probes IndexedDB, which React Native lacks, so without this the queue
+ * stays in memory and is lost on reload). `getAuthHeaders` is a generic escape
+ * hatch for a custom credential header on both the HTTP RPC path and the
+ * WebSocket upgrade; for better-auth sessions prefer a bearer token
+ * (`expoBearerToken` + the client's `setAuthToken` / `setWsToken`).
+ *
+ * The `persistence`, `fetch`, and `WebSocket` fields of `LunoraClientOptions`
+ * are still accepted and take precedence when you need full control; the two
+ * conveniences are sugar over exactly those seams.
+ * @experimental
+ */
 interface CreateLunoraClientOptions extends LunoraClientOptions {
   /**
-  * Attaches a credential to every HTTP RPC request and to the WebSocket
-  * upgrade request. See `AuthHeadersFactory`. When omitted, requests go out
-  * with only whatever `LunoraClient` already sets (its bearer token from
-  * `setAuthToken`, if any).
-  *
-  * Merged UNDER the client's own headers on the HTTP path (an explicit
-  * `setAuthToken` bearer wins over a same-named header here); applied to the
-  * WebSocket upgrade via a wrapping `WebSocket`, since the socket has no other
-  * way to carry credentials in React Native.
-  */
+   * Attaches a credential to every HTTP RPC request and to the WebSocket
+   * upgrade request. See `AuthHeadersFactory`. When omitted, requests go out
+   * with only whatever `LunoraClient` already sets (its bearer token from
+   * `setAuthToken`, if any).
+   *
+   * Merged UNDER the client's own headers on the HTTP path (an explicit
+   * `setAuthToken` bearer wins over a same-named header here); applied to the
+   * WebSocket upgrade via a wrapping `WebSocket`, since the socket has no other
+   * way to carry credentials in React Native.
+   */
   getAuthHeaders?: AuthHeadersFactory;
   /**
-  * React Native `AsyncStorage` (or any async key/value store with the same
-  * `getItem`/`setItem`/`removeItem` surface — Expo `SecureStore`, an in-memory
-  * map in tests). When supplied, the offline mutation queue is persisted here
-  * via `createAsyncStoragePersistence`, so writes made offline survive an app
-  * restart. Ignored when an explicit `persistence` is passed.
-  */
+   * React Native `AsyncStorage` (or any async key/value store with the same
+   * `getItem`/`setItem`/`removeItem` surface — Expo `SecureStore`, an in-memory
+   * map in tests). When supplied, the offline mutation queue is persisted here
+   * via `createAsyncStoragePersistence`, so writes made offline survive an app
+   * restart. Ignored when an explicit `persistence` is passed.
+   */
   storage?: AsyncStorageLike;
 }
 /**
-* Construct a `LunoraClient` tuned for React Native / Expo — a thin wrapper over
-* `new LunoraClient(options)` that fills in the two things a browser gets for
-* free but React Native does not.
-*
-* First, a durable offline queue: pass `storage` (React Native `AsyncStorage`,
-* or any async key/value store) and the offline mutation queue is persisted
-* through `createAsyncStoragePersistence` — the browser default auto-probes
-* IndexedDB, which React Native lacks, so without this the queue lives only in
-* memory and is lost on reload.
-*
-* Second, credentialed requests: pass `getAuthHeaders` and the returned headers
-* ride both the HTTP RPC path and the WebSocket upgrade, since React Native has
-* no cookie jar to attach a session implicitly.
-*
-* Everything on `LunoraClientOptions` is still accepted and passed through; an
-* explicit `persistence`, `fetch`, or `WebSocket` takes precedence over the
-* convenience derived from `storage` / `getAuthHeaders`. See the package README
-* for a full setup example.
-* @experimental
-*/
+ * Construct a `LunoraClient` tuned for React Native / Expo — a thin wrapper over
+ * `new LunoraClient(options)` that fills in the two things a browser gets for
+ * free but React Native does not.
+ *
+ * First, a durable offline queue: pass `storage` (React Native `AsyncStorage`,
+ * or any async key/value store) and the offline mutation queue is persisted
+ * through `createAsyncStoragePersistence` — the browser default auto-probes
+ * IndexedDB, which React Native lacks, so without this the queue lives only in
+ * memory and is lost on reload.
+ *
+ * Second, credentialed requests: pass `getAuthHeaders` and the returned headers
+ * ride both the HTTP RPC path and the WebSocket upgrade, since React Native has
+ * no cookie jar to attach a session implicitly.
+ *
+ * Everything on `LunoraClientOptions` is still accepted and passed through; an
+ * explicit `persistence`, `fetch`, or `WebSocket` takes precedence over the
+ * convenience derived from `storage` / `getAuthHeaders`. See the package README
+ * for a full setup example.
+ * @experimental
+ */
 declare const createLunoraClient: (options: CreateLunoraClientOptions) => LunoraClient;
 export { type AuthHeadersFactory, type CreateLunoraClientOptions, createLunoraClient };

package/dist/index.d.ts

@@ -1,78 +1,78 @@
 import { AsyncStorageLike, LunoraClientOptions, LunoraClient } from '@lunora/client';
 export * from '@lunora/react';
 /**
-* A `() => headers` factory the React Native client threads onto every HTTP RPC
-* request *and* the WebSocket upgrade — a generic escape hatch for attaching a
-* **custom** credential header (an API-gateway key, a proxy token, …) that
-* React Native's missing cookie jar can't carry implicitly. Return `undefined`
-* (or an empty object) when there's nothing to attach.
-*
-* For better-auth Expo sessions, prefer a **bearer** token instead: read it with
-* `@lunora/react-native/auth`'s `expoBearerToken` and feed it to
-* `client.setAuthToken` / `setWsToken` (see the package README). A bearer avoids
-* the `Cookie` header the runtime's CSRF guard rejects on `Origin`-less native
-* requests.
-* @experimental
-*/
+ * A `() => headers` factory the React Native client threads onto every HTTP RPC
+ * request *and* the WebSocket upgrade — a generic escape hatch for attaching a
+ * **custom** credential header (an API-gateway key, a proxy token, …) that
+ * React Native's missing cookie jar can't carry implicitly. Return `undefined`
+ * (or an empty object) when there's nothing to attach.
+ *
+ * For better-auth Expo sessions, prefer a **bearer** token instead: read it with
+ * `@lunora/react-native/auth`'s `expoBearerToken` and feed it to
+ * `client.setAuthToken` / `setWsToken` (see the package README). A bearer avoids
+ * the `Cookie` header the runtime's CSRF guard rejects on `Origin`-less native
+ * requests.
+ * @experimental
+ */
 type AuthHeadersFactory = () => Record<string, string> | undefined;
 /**
-* Options for `createLunoraClient` — the React Native / Expo counterpart to
-* constructing a `LunoraClient` directly. It is `LunoraClientOptions` with two
-* React-Native-shaped conveniences layered on. `storage` wires the
-* AsyncStorage-backed offline-queue persistence for you (the browser default
-* auto-probes IndexedDB, which React Native lacks, so without this the queue
-* stays in memory and is lost on reload). `getAuthHeaders` is a generic escape
-* hatch for a custom credential header on both the HTTP RPC path and the
-* WebSocket upgrade; for better-auth sessions prefer a bearer token
-* (`expoBearerToken` + the client's `setAuthToken` / `setWsToken`).
-*
-* The `persistence`, `fetch`, and `WebSocket` fields of `LunoraClientOptions`
-* are still accepted and take precedence when you need full control; the two
-* conveniences are sugar over exactly those seams.
-* @experimental
-*/
+ * Options for `createLunoraClient` — the React Native / Expo counterpart to
+ * constructing a `LunoraClient` directly. It is `LunoraClientOptions` with two
+ * React-Native-shaped conveniences layered on. `storage` wires the
+ * AsyncStorage-backed offline-queue persistence for you (the browser default
+ * auto-probes IndexedDB, which React Native lacks, so without this the queue
+ * stays in memory and is lost on reload). `getAuthHeaders` is a generic escape
+ * hatch for a custom credential header on both the HTTP RPC path and the
+ * WebSocket upgrade; for better-auth sessions prefer a bearer token
+ * (`expoBearerToken` + the client's `setAuthToken` / `setWsToken`).
+ *
+ * The `persistence`, `fetch`, and `WebSocket` fields of `LunoraClientOptions`
+ * are still accepted and take precedence when you need full control; the two
+ * conveniences are sugar over exactly those seams.
+ * @experimental
+ */
 interface CreateLunoraClientOptions extends LunoraClientOptions {
   /**
-  * Attaches a credential to every HTTP RPC request and to the WebSocket
-  * upgrade request. See `AuthHeadersFactory`. When omitted, requests go out
-  * with only whatever `LunoraClient` already sets (its bearer token from
-  * `setAuthToken`, if any).
-  *
-  * Merged UNDER the client's own headers on the HTTP path (an explicit
-  * `setAuthToken` bearer wins over a same-named header here); applied to the
-  * WebSocket upgrade via a wrapping `WebSocket`, since the socket has no other
-  * way to carry credentials in React Native.
-  */
+   * Attaches a credential to every HTTP RPC request and to the WebSocket
+   * upgrade request. See `AuthHeadersFactory`. When omitted, requests go out
+   * with only whatever `LunoraClient` already sets (its bearer token from
+   * `setAuthToken`, if any).
+   *
+   * Merged UNDER the client's own headers on the HTTP path (an explicit
+   * `setAuthToken` bearer wins over a same-named header here); applied to the
+   * WebSocket upgrade via a wrapping `WebSocket`, since the socket has no other
+   * way to carry credentials in React Native.
+   */
   getAuthHeaders?: AuthHeadersFactory;
   /**
-  * React Native `AsyncStorage` (or any async key/value store with the same
-  * `getItem`/`setItem`/`removeItem` surface — Expo `SecureStore`, an in-memory
-  * map in tests). When supplied, the offline mutation queue is persisted here
-  * via `createAsyncStoragePersistence`, so writes made offline survive an app
-  * restart. Ignored when an explicit `persistence` is passed.
-  */
+   * React Native `AsyncStorage` (or any async key/value store with the same
+   * `getItem`/`setItem`/`removeItem` surface — Expo `SecureStore`, an in-memory
+   * map in tests). When supplied, the offline mutation queue is persisted here
+   * via `createAsyncStoragePersistence`, so writes made offline survive an app
+   * restart. Ignored when an explicit `persistence` is passed.
+   */
   storage?: AsyncStorageLike;
 }
 /**
-* Construct a `LunoraClient` tuned for React Native / Expo — a thin wrapper over
-* `new LunoraClient(options)` that fills in the two things a browser gets for
-* free but React Native does not.
-*
-* First, a durable offline queue: pass `storage` (React Native `AsyncStorage`,
-* or any async key/value store) and the offline mutation queue is persisted
-* through `createAsyncStoragePersistence` — the browser default auto-probes
-* IndexedDB, which React Native lacks, so without this the queue lives only in
-* memory and is lost on reload.
-*
-* Second, credentialed requests: pass `getAuthHeaders` and the returned headers
-* ride both the HTTP RPC path and the WebSocket upgrade, since React Native has
-* no cookie jar to attach a session implicitly.
-*
-* Everything on `LunoraClientOptions` is still accepted and passed through; an
-* explicit `persistence`, `fetch`, or `WebSocket` takes precedence over the
-* convenience derived from `storage` / `getAuthHeaders`. See the package README
-* for a full setup example.
-* @experimental
-*/
+ * Construct a `LunoraClient` tuned for React Native / Expo — a thin wrapper over
+ * `new LunoraClient(options)` that fills in the two things a browser gets for
+ * free but React Native does not.
+ *
+ * First, a durable offline queue: pass `storage` (React Native `AsyncStorage`,
+ * or any async key/value store) and the offline mutation queue is persisted
+ * through `createAsyncStoragePersistence` — the browser default auto-probes
+ * IndexedDB, which React Native lacks, so without this the queue lives only in
+ * memory and is lost on reload.
+ *
+ * Second, credentialed requests: pass `getAuthHeaders` and the returned headers
+ * ride both the HTTP RPC path and the WebSocket upgrade, since React Native has
+ * no cookie jar to attach a session implicitly.
+ *
+ * Everything on `LunoraClientOptions` is still accepted and passed through; an
+ * explicit `persistence`, `fetch`, or `WebSocket` takes precedence over the
+ * convenience derived from `storage` / `getAuthHeaders`. See the package README
+ * for a full setup example.
+ * @experimental
+ */
 declare const createLunoraClient: (options: CreateLunoraClientOptions) => LunoraClient;
 export { type AuthHeadersFactory, type CreateLunoraClientOptions, createLunoraClient };

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lunora/react-native",
-  "version": "1.0.0-alpha.3",
+  "version": "1.0.0-alpha.5",
   "description": "React Native / Expo integration for Lunora: an AsyncStorage-backed client factory, the useQuery/useMutation/useSubscription hooks, and a one-call better-auth Expo client",
   "keywords": [
     "cloudflare",
@@ -50,8 +50,8 @@
     "access": "public"
   },
   "dependencies": {
-    "@lunora/client": "1.0.0-alpha.23",
-    "@lunora/react": "1.0.0-alpha.27"
+    "@lunora/client": "1.0.0-alpha.25",
+    "@lunora/react": "1.0.0-alpha.29"
   },
   "peerDependencies": {
     "@better-auth/expo": "^1.6.23",