@vennbase/react 0.1.8

package/LICENSE

@@ -0,0 +1,183 @@
+Apache License
+Version 2.0, January 2004
+http://www.apache.org/licenses/
+
+TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+1. Definitions.
+
+"License" shall mean the terms and conditions for use, reproduction, and
+distribution as defined by Sections 1 through 9 of this document.
+
+"Licensor" shall mean the copyright owner or entity authorized by the copyright
+owner that is granting the License.
+
+"Legal Entity" shall mean the union of the acting entity and all other entities
+that control, are controlled by, or are under common control with that entity.
+For the purposes of this definition, "control" means (i) the power, direct or
+indirect, to cause the direction or management of such entity, whether by
+contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the
+outstanding shares, or (iii) beneficial ownership of such entity.
+
+"You" (or "Your") shall mean an individual or Legal Entity exercising
+permissions granted by this License.
+
+"Source" form shall mean the preferred form for making modifications, including
+but not limited to software source code, documentation source, and configuration
+files.
+
+"Object" form shall mean any form resulting from mechanical transformation or
+translation of a Source form, including but not limited to compiled object code,
+generated documentation, and conversions to other media types.
+
+"Work" shall mean the work of authorship, whether in Source or Object form, made
+available under the License, as indicated by a copyright notice that is included
+in or attached to the work (an example is provided in the Appendix below).
+
+"Derivative Works" shall mean any work, whether in Source or Object form, that
+is based on (or derived from) the Work and for which the editorial revisions,
+annotations, elaborations, or other modifications represent, as a whole, an
+original work of authorship. For the purposes of this License, Derivative Works
+shall not include works that remain separable from, or merely link (or bind by
+name) to the interfaces of, the Work and Derivative Works thereof.
+
+"Contribution" shall mean any work of authorship, including the original version
+of the Work and any modifications or additions to that Work or Derivative Works
+thereof, that is intentionally submitted to Licensor for inclusion in the Work
+by the copyright owner or by an individual or Legal Entity authorized to submit
+on behalf of the copyright owner. For the purposes of this definition,
+"submitted" means any form of electronic, verbal, or written communication sent
+to the Licensor or its representatives, including but not limited to
+communication on electronic mailing lists, source code control systems, and
+issue tracking systems that are managed by, or on behalf of, the Licensor for
+the purpose of discussing and improving the Work, but excluding communication
+that is conspicuously marked or otherwise designated in writing by the copyright
+owner as "Not a Contribution."
+
+"Contributor" shall mean Licensor and any individual or Legal Entity on behalf
+of whom a Contribution has been received by Licensor and subsequently
+incorporated within the Work.
+
+2. Grant of Copyright License. Subject to the terms and conditions of this
+License, each Contributor hereby grants to You a perpetual, worldwide,
+non-exclusive, no-charge, royalty-free, irrevocable copyright license to
+reproduce, prepare Derivative Works of, publicly display, publicly perform,
+sublicense, and distribute the Work and such Derivative Works in Source or
+Object form.
+
+3. Grant of Patent License. Subject to the terms and conditions of this License,
+each Contributor hereby grants to You a perpetual, worldwide, non-exclusive,
+no-charge, royalty-free, irrevocable (except as stated in this section) patent
+license to make, have made, use, offer to sell, sell, import, and otherwise
+transfer the Work, where such license applies only to those patent claims
+licensable by such Contributor that are necessarily infringed by their
+Contribution(s) alone or by combination of their Contribution(s) with the Work
+to which such Contribution(s) was submitted. If You institute patent litigation
+against any entity (including a cross-claim or counterclaim in a lawsuit)
+alleging that the Work or a Contribution incorporated within the Work
+constitutes direct or contributory patent infringement, then any patent licenses
+granted to You under this License for that Work shall terminate as of the date
+such litigation is filed.
+
+4. Redistribution. You may reproduce and distribute copies of the Work or
+Derivative Works thereof in any medium, with or without modifications, and in
+Source or Object form, provided that You meet the following conditions:
+
+(a) You must give any other recipients of the Work or Derivative Works a copy of
+this License; and
+
+(b) You must cause any modified files to carry prominent notices stating that
+You changed the files; and
+
+(c) You must retain, in the Source form of any Derivative Works that You
+distribute, all copyright, patent, trademark, and attribution notices from the
+Source form of the Work, excluding those notices that do not pertain to any part
+of the Derivative Works; and
+
+(d) If the Work includes a "NOTICE" text file as part of its distribution, then
+any Derivative Works that You distribute must include a readable copy of the
+attribution notices contained within such NOTICE file, excluding those notices
+that do not pertain to any part of the Derivative Works, in at least one of the
+following places: within a NOTICE text file distributed as part of the
+Derivative Works; within the Source form or documentation, if provided along
+with the Derivative Works; or, within a display generated by the Derivative
+Works, if and wherever such third-party notices normally appear. The contents of
+the NOTICE file are for informational purposes only and do not modify the
+License. You may add Your own attribution notices within Derivative Works that
+You distribute, alongside or as an addendum to the NOTICE text from the Work,
+provided that such additional attribution notices cannot be construed as
+modifying the License.
+
+You may add Your own copyright statement to Your modifications and may provide
+additional or different license terms and conditions for use, reproduction, or
+distribution of Your modifications, or for any such Derivative Works as a whole,
+provided Your use, reproduction, and distribution of the Work otherwise complies
+with the conditions stated in this License.
+
+5. Submission of Contributions. Unless You explicitly state otherwise, any
+Contribution intentionally submitted for inclusion in the Work by You to the
+Licensor shall be under the terms and conditions of this License, without any
+additional terms or conditions. Notwithstanding the above, nothing herein shall
+supersede or modify the terms of any separate license agreement you may have
+executed with Licensor regarding such Contributions.
+
+6. Trademarks. This License does not grant permission to use the trade names,
+trademarks, service marks, or product names of the Licensor, except as required
+for reasonable and customary use in describing the origin of the Work and
+reproducing the content of the NOTICE file.
+
+7. Disclaimer of Warranty. Unless required by applicable law or agreed to in
+writing, Licensor provides the Work (and each Contributor provides its
+Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+KIND, either express or implied, including, without limitation, any warranties
+or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+PARTICULAR PURPOSE. You are solely responsible for determining the
+appropriateness of using or redistributing the Work and assume any risks
+associated with Your exercise of permissions under this License.
+
+8. Limitation of Liability. In no event and under no legal theory, whether in
+tort (including negligence), contract, or otherwise, unless required by
+applicable law (such as deliberate and grossly negligent acts) or agreed to in
+writing, shall any Contributor be liable to You for damages, including any
+direct, indirect, special, incidental, or consequential damages of any character
+arising as a result of this License or out of the use or inability to use the
+Work (including but not limited to damages for loss of goodwill, work stoppage,
+computer failure or malfunction, or any and all other commercial damages or
+losses), even if such Contributor has been advised of the possibility of such
+damages.
+
+9. Accepting Warranty or Additional Liability. While redistributing the Work or
+Derivative Works thereof, You may choose to offer, and charge a fee for,
+acceptance of support, warranty, indemnity, or other liability obligations
+and/or rights consistent with this License. However, in accepting such
+obligations, You may act only on Your own behalf and on Your sole responsibility,
+not on behalf of any other Contributor, and only if You agree to indemnify,
+defend, and hold each Contributor harmless for any liability incurred by, or
+claims asserted against, such Contributor by reason of your accepting any such
+warranty or additional liability.
+
+END OF TERMS AND CONDITIONS
+
+APPENDIX: How to apply the Apache License to your work.
+
+To apply the Apache License to your work, attach the following boilerplate
+notice, with the fields enclosed by brackets "[]" replaced with your own
+identifying information. (Don't include the brackets!) The text should be
+enclosed in the appropriate comment syntax for the file format. We also
+recommend that a file or class name and description of purpose be included on the
+same "printed page" as the copyright notice for easier identification within
+third-party archives.
+
+Copyright [yyyy] [name of copyright owner]
+
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+
+    http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.

package/README.md

@@ -0,0 +1,365 @@
+# @vennbase/react
+
+React hooks and provider for [Vennbase](https://www.npmjs.com/package/@vennbase/core) — a multi-user database for apps that have no backend. Users sign in with their [Puter](https://puter.com) accounts. Their data lives in their Puter storage.
+
+See [`@vennbase/core`](https://www.npmjs.com/package/@vennbase/core) for the full API and schema documentation.
+
+## Install
+
+```bash
+pnpm add @vennbase/react @vennbase/core
+```
+
+## Setup
+
+Create one `Vennbase` instance for your app.
+
+```tsx
+import { Vennbase } from "@vennbase/core";
+import { schema } from "./schema";
+
+const db = new Vennbase({ schema, appBaseUrl: window.location.origin });
+```
+
+If you want to read the Vennbase instance from React context once, wrap your app in `<VennbaseProvider>` and call `useVennbase()` where needed:
+
+```tsx
+import { VennbaseProvider, useVennbase, useSession } from "@vennbase/react";
+
+export function App() {
+  return (
+    <VennbaseProvider db={db}>
+      <AppShell />
+    </VennbaseProvider>
+  );
+}
+
+function AppShell() {
+  const db = useVennbase<Schema>();
+  const session = useSession(db);
+  return <Main session={session} />;
+}
+```
+
+## Auth
+
+Use `useSession` to gate your UI on the auth state:
+
+```tsx
+import { useSession } from "@vennbase/react";
+import { db } from "./db";
+
+function AppShell() {
+  const session = useSession(db);
+
+  if (session.status === "loading") return <p>Checking session…</p>;
+
+  if (!session.session?.signedIn) {
+    return <button onClick={() => void session.signIn()}>Log in with Puter</button>;
+  }
+
+  return <Main />;
+}
+```
+
+## Querying
+
+`useQuery` polls for changes and re-renders automatically. `rows` is always a typed array — never `undefined`.
+
+`useQuery(db, "games", ...)` never means "all accessible games". If a collection is not declared as `in: ["user"]`, omitting `in` is an error.
+
+```tsx
+import { useQuery } from "@vennbase/react";
+import { db } from "./db";
+
+function CardList({ board }: { board: BoardHandle }) {
+  const { rows: cards } = useQuery<Schema, "cards">(db, "cards", {
+    in: board,
+    index: "byCreatedAt",
+    order: "asc",
+  });
+
+  return (
+    <ul>
+      {cards.map((card) => (
+        <li key={card.id}>{card.fields.text}</li>
+      ))}
+    </ul>
+  );
+}
+```
+
+Collections declared as `in: ["user"]` keep the same ergonomics in React: if you omit `in`, Vennbase queries inside the current signed-in user's built-in `user` row.
+
+```tsx
+function RecentBoards() {
+  const { rows: recentBoards } = useQuery<Schema, "recentBoards">(db, "recentBoards", {
+    index: "byOpenedAt",
+    order: "desc",
+    limit: 10,
+  });
+
+  return (
+    <ul>
+      {recentBoards.map((recentBoard) => (
+        <li key={recentBoard.id}>{recentBoard.fields.boardRef.id}</li>
+      ))}
+    </ul>
+  );
+}
+```
+
+## Single-row reads
+
+`useRow` is the single-row equivalent of `useQuery`: it polls for changes and re-renders automatically.
+
+If you need one row in React, prefer `useRow(db, row)` over calling `db.getRow(...)` in an effect and wiring your own polling loop. `row` can be either a `RowHandle` or a `RowRef`.
+
+```tsx
+import { useRow } from "@vennbase/react";
+import { db } from "./db";
+import type { RowRef } from "@vennbase/core";
+
+function BoardTitle({ boardRef }: { boardRef: RowRef<"boards"> }) {
+  const { data: board, status } = useRow<Schema, "boards">(db, boardRef);
+
+  if (status !== "success" || !board) return <p>Loading…</p>;
+  return <h1>{board.fields.title}</h1>;
+}
+```
+
+## Row Handle Identity
+
+`useRow` and `useQuery` keep `RowHandle` identity stable for the life of a row within a `Vennbase` instance. When the row fields change, the same handle object is reused and `row.fields` is replaced with a fresh snapshot object.
+
+That means using `[row]` as an effect dependency is safe for subscriptions keyed to the logical row. If your effect depends on row contents, depend on `row.fields` or specific field values instead.
+
+```tsx
+useEffect(() => {
+  if (!row) return;
+  const connection = row.connectCrdt(callbacks);
+  return () => connection.disconnect();
+}, [row]);
+```
+
+```tsx
+useEffect(() => {
+  if (!row) return;
+  syncForm(row.fields);
+}, [row?.fields]);
+```
+
+## CRDT adapters
+
+Use row fields for queryable metadata and the CRDT document for collaborative value state.
+
+`useCrdt` wires any `CrdtAdapter` to a row. For Yjs, inject the app's own `Y` instance so `@vennbase/yjs` never loads a second runtime:
+
+```tsx
+import * as Y from "yjs";
+import { useRef } from "react";
+import { useCrdt } from "@vennbase/react";
+import { createYjsAdapter } from "@vennbase/yjs";
+
+function Room({ row }: { row: BoardHandle | null }) {
+  const adapterRef = useRef(createYjsAdapter(Y));
+  const { value: doc, version } = useCrdt(row, adapterRef.current);
+
+  const entries = doc.getArray<string>("messages").toArray();
+  return <pre data-version={version}>{JSON.stringify(entries)}</pre>;
+}
+```
+
+## Invite links
+
+`useShareLink` lazily generates (or reuses) a share link for a row. `useAcceptInviteFromUrl` handles the recipient side: it detects Vennbase invite URLs in the current URL, waits for the session, calls `acceptInvite`, waits for `onOpen`, and then clears the invite params.
+
+```tsx
+import { useShareLink, useAcceptInviteFromUrl } from "@vennbase/react";
+import { db } from "./db";
+
+// Sharer side
+function ShareButton({ board }: { board: BoardHandle }) {
+  const { shareLink } = useShareLink(db, board);
+  return <button onClick={() => navigator.clipboard.writeText(shareLink ?? "")}>Copy share link</button>;
+}
+
+// Recipient side — call once near the app root
+function InviteHandler() {
+  useAcceptInviteFromUrl(db, {
+    onOpen: (board) => {
+      // navigate to the shared board
+    },
+  });
+  return null;
+}
+```
+
+## Mutations
+
+`useMutation` wraps any async call with `loading` / `success` / `error` state:
+
+```tsx
+import { useMutation } from "@vennbase/react";
+
+function AddCard({ board }: { board: BoardHandle }) {
+  const { mutate: addCard, status } = useMutation(async (text: string) => {
+    const write = db.create("cards", { text, done: false, createdAt: Date.now() }, { in: board });
+    await write.committed;
+    return write.value;
+  });
+
+  return (
+    <button disabled={status === "loading"} onClick={() => addCard("New card")}>
+      Add card
+    </button>
+  );
+}
+```
+
+## Hook reference
+
+| Hook | Arguments | Returns |
+|------|-----------|---------|
+| `useSession(db)` | `Vennbase` instance | `{ session, status, isRefreshing, error, refreshError, signIn, refresh }` |
+| `useCurrentUser(db)` | `Vennbase` instance | `{ data: VennbaseUser, status, isRefreshing, error, refreshError, refresh }` |
+| `useVennbase()` | — | `Vennbase` instance from context |
+| `useVennbaseReady(db)` | `Vennbase` instance | `{ status, isRefreshing, error, refreshError, refresh }` — resolves when auth + provisioning complete |
+| `useQuery(db, collection, options)` | db, collection name, query options | `{ rows, data, status, isRefreshing, error, refreshError, refresh }` |
+| `useRow(db, row)` | db, row handle or row ref | `{ data: RowHandle, status, isRefreshing, error, refreshError, refresh }` |
+| `useParents(db, row)` | db, row handle or row ref | `{ data: RowRef[], status, isRefreshing, error, refreshError, refresh }` |
+| `useMemberUsernames(db, row)` | db, row handle or row ref | `{ data: string[], status, isRefreshing, error, refreshError, refresh }` |
+| `useDirectMembers(db, row)` | db, row handle or row ref | `{ data: { username, role }[], status, isRefreshing, error, refreshError, refresh }` |
+| `useEffectiveMembers(db, row)` | db, row handle or row ref | `{ data: DbMemberInfo[], status, isRefreshing, error, refreshError, refresh }` |
+| `useShareLink(db, row)` | db, row handle or row ref | `{ shareLink: string, status, isRefreshing, error, refreshError, refresh }` |
+| `useAcceptInviteFromUrl(db, options?)` | db, `{ url?, clearInviteParams?, onOpen?, accept? }` | `{ hasInvite, inviteInput, data, status, isRefreshing, error, refreshError, refresh }` |
+| `useSavedRow(db, options)` | db, `{ key, url?, clearInviteParams?, loadSavedRow?, acceptInvite?, getRow? }` | `{ hasInvite, inviteInput, data, status, isRefreshing, error, refreshError, refresh, save, clear }` |
+| `useMutation(fn)` | async function | `{ mutate, data, status, error, reset }` |
+
+All data-fetching hooks return `status: "idle" | "loading" | "success" | "error"`. `loading` means there is no usable data yet. Once a hook has usable data, it stays `success` during background reloads and exposes that work through `isRefreshing` / `refreshError`.
+
+## Commonly used types reference
+
+```ts
+interface UseHookOptions {
+  enabled?: boolean;
+}
+
+interface UseResourceResult<TData> {
+  data: TData | undefined;
+  error: unknown;
+  refreshError: unknown;
+  isRefreshing: boolean;
+  status: "idle" | "loading" | "success" | "error";
+  refresh(): Promise<void>;
+}
+
+interface UseQueryResult<TRow> extends UseResourceResult<TRow[]> {
+  rows: TRow[];
+}
+```
+
+### `useQuery`
+
+```ts
+function useQuery<
+  Schema extends DbSchema,
+  TCollection extends CollectionName<Schema>,
+>(
+  db: Vennbase<Schema>,
+  collection: TCollection,
+  options: DbQueryOptions<Schema, TCollection> | null | undefined,
+  hookOptions?: UseHookOptions,
+): UseQueryResult<
+  RowHandle<Schema, TCollection>
+>
+```
+
+- `options: null | undefined` keeps the hook idle.
+- `rows` is always an array and mirrors `data ?? []`.
+- The row type matches `db.query(...)`, including parent collection constraints.
+
+### `useRow`
+
+```ts
+function useRow<
+  Schema extends DbSchema,
+  TCollection extends CollectionName<Schema>,
+>(
+  db: Vennbase<Schema>,
+  row: RowInput<TCollection> | null | undefined,
+  hookOptions?: UseHookOptions,
+): UseResourceResult<
+  RowHandle<Schema, TCollection>
+>
+```
+
+- `row: null | undefined` keeps the hook idle.
+- `row` can be either a `RowHandle` or `RowRef`.
+- `useRow` polls for changes and re-renders automatically. In React, prefer it over manual polling around `db.getRow(...)`.
+- The returned handle matches `db.getRow(...)`, including parent collection constraints.
+
+### `useShareLink`
+
+```ts
+function useShareLink<Schema extends DbSchema>(
+  db: Vennbase<Schema>,
+  row: RowInput | null | undefined,
+  options?: UseHookOptions,
+): {
+  shareLink: string | undefined;
+  ...
+}
+```
+
+- `row: null | undefined` keeps the hook idle.
+- `row` can be either a `RowHandle` or `RowRef`.
+- `shareLink` is the generated or reused invite URL for the row.
+
+### `useAcceptInviteFromUrl`
+
+```ts
+interface UseAcceptInviteFromUrlOptions<
+  Schema extends DbSchema,
+  TResult = AnyRowHandle<Schema>,
+> extends UseHookOptions {
+  url?: string | null;
+  clearInviteParams?: boolean | ((url: URL) => string);
+  onOpen?: (result: TResult) => void | Promise<void>;
+  accept?: (inviteInput: string, db: Vennbase<Schema>) => Promise<TResult>;
+}
+
+interface UseAcceptInviteFromUrlResult<TResult> extends UseResourceResult<TResult> {
+  hasInvite: boolean;
+  inviteInput: string | null;
+}
+
+function useAcceptInviteFromUrl<
+  Schema extends DbSchema,
+  TResult = AnyRowHandle<Schema>,
+>(
+  db: Vennbase<Schema>,
+  options?: UseAcceptInviteFromUrlOptions<Schema, TResult>,
+): UseAcceptInviteFromUrlResult<TResult>
+```
+
+- `url` defaults to `window.location.href`.
+- `clearInviteParams` defaults to `true`.
+- `onOpen` runs after invite acceptance succeeds and may be async.
+- The hook stays in `loading` until `onOpen` finishes and the invite params are removed from the current URL.
+- Override `accept` when invite acceptance should return something other than `db.acceptInvite(...)`.
+
+### `useMutation`
+
+```ts
+function useMutation<TArgs extends unknown[], TResult>(
+  fn: (...args: TArgs) => Promise<TResult>,
+): {
+  mutate: (...args: TArgs) => Promise<TResult>;
+  data: TResult | undefined;
+  status: "idle" | "loading" | "success" | "error";
+  error: unknown;
+  reset(): void;
+}
+```
+- Use it to wrap writes like `db.create(...)`, `db.update(...)`, or any other async workflow you want to expose as a React action state.

package/dist/index.d.ts

@@ -0,0 +1,90 @@
+import { type ReactNode } from "react";
+import type { Vennbase } from "@vennbase/core";
+import type { AuthSession, AnyRowHandle, CollectionName, CrdtAdapter, CrdtConnectCallbacks, CrdtConnection, DbMemberInfo, DbQueryOptions, DbSchema, MemberRole, VennbaseUser, RowRef, RowInput } from "@vennbase/core";
+import type { RowHandle } from "@vennbase/core";
+import type { ActivitySubscriber } from "./polling";
+import { type LoadStatus, type ResourceSnapshot } from "./runtime";
+export type { ActivitySubscriber } from "./polling";
+export type { LoadStatus } from "./runtime";
+export interface UseResourceResult<TData> extends ResourceSnapshot<TData> {
+    refresh(): Promise<void>;
+}
+export interface UseQueryResult<TRow> extends UseResourceResult<TRow[]> {
+    rows: TRow[];
+}
+export type UseShareLinkResult = Omit<UseResourceResult<string>, "data"> & {
+    shareLink: string | undefined;
+};
+export interface UseSessionResult extends UseResourceResult<AuthSession> {
+    session: AuthSession | undefined;
+    signIn(): Promise<VennbaseUser>;
+}
+export interface UseCrdtResult<TValue> {
+    value: TValue;
+    version: number;
+    status: "idle" | "connected";
+    flush(): Promise<void>;
+}
+export interface UseHookOptions {
+    enabled?: boolean;
+}
+export interface UseAcceptInviteFromUrlOptions<Schema extends DbSchema, TResult = AnyRowHandle<Schema>> extends UseHookOptions {
+    url?: string | null;
+    clearInviteParams?: boolean | ((url: URL) => string);
+    onOpen?: (result: TResult) => void | Promise<void>;
+    accept?: (inviteInput: string, db: Vennbase<Schema>) => Promise<TResult>;
+}
+export interface UseAcceptInviteFromUrlResult<TResult> extends UseResourceResult<TResult> {
+    hasInvite: boolean;
+    inviteInput: string | null;
+}
+export interface UseSavedRowOptions<Schema extends DbSchema, TResult = AnyRowHandle<Schema>> extends UseHookOptions {
+    key: string;
+    url?: string | null;
+    clearInviteParams?: boolean | ((url: URL) => string);
+    loadSavedRow?: (row: AnyRowHandle<Schema>, db: Vennbase<Schema>) => Promise<TResult> | TResult;
+    acceptInvite?: (inviteInput: string, db: Vennbase<Schema>) => Promise<TResult>;
+    getRow?: (result: TResult) => RowRef;
+}
+export interface UseSavedRowResult<TResult> extends UseResourceResult<TResult | null> {
+    hasInvite: boolean;
+    inviteInput: string | null;
+    save(result: TResult): Promise<void>;
+    clear(): Promise<void>;
+}
+export interface VennbaseProviderProps<Schema extends DbSchema> {
+    children: ReactNode;
+    db: Vennbase<Schema>;
+    subscribeToActivity?: ActivitySubscriber;
+    client?: never;
+}
+interface CrdtRowLike {
+    ref: RowRef;
+    connectCrdt(callbacks: CrdtConnectCallbacks): CrdtConnection;
+}
+export declare function VennbaseProvider<Schema extends DbSchema>({ children, db, subscribeToActivity, }: VennbaseProviderProps<Schema>): import("react/jsx-runtime").JSX.Element;
+export declare function useVennbase<Schema extends DbSchema>(): Vennbase<Schema>;
+export declare function useCrdt<TValue>(row: CrdtRowLike | null | undefined, adapter: CrdtAdapter<TValue>): UseCrdtResult<TValue>;
+export declare function useVennbaseReady<Schema extends DbSchema>(db: Vennbase<Schema>, options?: UseHookOptions): UseResourceResult<void>;
+export declare function useSession<Schema extends DbSchema>(db: Vennbase<Schema>, options?: UseHookOptions): UseSessionResult;
+export declare function useCurrentUser<Schema extends DbSchema>(db: Vennbase<Schema>, options?: UseHookOptions): UseResourceResult<VennbaseUser>;
+export declare function useQuery<Schema extends DbSchema, TCollection extends CollectionName<Schema>>(db: Vennbase<Schema>, collection: TCollection, options: DbQueryOptions<Schema, TCollection> | null | undefined, hookOptions?: UseHookOptions): UseQueryResult<RowHandle<Schema, TCollection>>;
+export declare function useRow<Schema extends DbSchema, TCollection extends CollectionName<Schema>>(db: Vennbase<Schema>, row: RowInput<TCollection> | null | undefined, options?: UseHookOptions): UseResourceResult<RowHandle<Schema, TCollection>>;
+export declare function useParents<Schema extends DbSchema>(db: Vennbase<Schema>, row: RowInput | null | undefined, options?: UseHookOptions): UseResourceResult<Array<RowRef>>;
+export declare function useMemberUsernames<Schema extends DbSchema>(db: Vennbase<Schema>, row: RowInput | null | undefined, options?: UseHookOptions): UseResourceResult<string[]>;
+export declare function useDirectMembers<Schema extends DbSchema>(db: Vennbase<Schema>, row: RowInput | null | undefined, options?: UseHookOptions): UseResourceResult<Array<{
+    username: string;
+    role: MemberRole;
+}>>;
+export declare function useEffectiveMembers<Schema extends DbSchema>(db: Vennbase<Schema>, row: RowInput | null | undefined, options?: UseHookOptions): UseResourceResult<Array<DbMemberInfo<Schema>>>;
+export declare function useShareLink<Schema extends DbSchema>(db: Vennbase<Schema>, row: RowInput | null | undefined, options?: UseHookOptions): UseShareLinkResult;
+export declare function useAcceptInviteFromUrl<Schema extends DbSchema, TResult = AnyRowHandle<Schema>>(db: Vennbase<Schema>, options?: UseAcceptInviteFromUrlOptions<Schema, TResult>): UseAcceptInviteFromUrlResult<TResult>;
+export declare function useSavedRow<Schema extends DbSchema, TResult = AnyRowHandle<Schema>>(db: Vennbase<Schema>, options: UseSavedRowOptions<Schema, TResult>): UseSavedRowResult<TResult>;
+export interface MutationResult<TResult, TArgs extends unknown[]> {
+    data: TResult | undefined;
+    error: unknown;
+    mutate: (...args: TArgs) => Promise<TResult>;
+    reset(): void;
+    status: Exclude<LoadStatus, "idle"> | "idle";
+}
+export declare function useMutation<TArgs extends unknown[], TResult>(mutation: (...args: TArgs) => Promise<TResult>): MutationResult<TResult, TArgs>;