@ic-reactor/react 1.0.5 → 1.0.7

package/dist/provider/agent.d.ts

@@ -1,71 +1,29 @@
-import type { AgentManagerParameters } from "../types";
-import type { CreateAgentContextReturnType } from "./types";
+/// <reference types="react" />
 /**
- * Creates a React context for managing IC agent and authentication states, providing hooks for interacting with the IC blockchain.
- * This function initializes an `AgentContext` with a set of utilities and hooks based on the provided agent configuration.
+ * `AgentProvider` is a React functional component that serves as a context provider for IC agent and authentication hooks.
+ * It enables any child components to access and use the agent and authentication functionalities seamlessly.
  *
- * @param agentParameters A partial configuration object for the agent manager, allowing customization of the agent's behavior.
+ * The provider encapsulates the logic for initializing and managing an agent manager instance, which is then used to
+ * create various hooks related to agent operations and authentication processes. These hooks are made available to all
+ * child components through the context, facilitating a centralized and efficient way to interact with the Internet Computer (IC) blockchain.
  *
- * @returns An object containing the `AgentProvider` component and various hooks for interacting with the agent and authentication state.
- * The `AgentProvider` component is a React context provider that should wrap your app or components needing access to agent functionalities.
- *
- * Usage:
- * - `AgentProvider`: React component to provide agent context to your application.
- * - `useAgent`, `useAuthClient`, `useAuthState`, `useAgentState`, `useAgentManager`, `useUserPrincipal`: Hooks extracted from the created context for managing agent and authentication state within components.
+ * @param children - Child components that can consume the context.
+ * @param agentManager - An optional `AgentManager` instance to be used by the provider. If not provided, a new instance
+ *                       will be created based on the provided options combined with default configuration.
+ * @param options - Configuration options for the `AgentManager`. These options are merged with any default configurations
+ *                  specified during the context creation and can include custom settings for the agent, such as identity,
+ *                  host URL, etc.
  *
  * @example
- * ```tsx
- * // agent.ts
- * import { createAgentContext } from "@ic-reactor/react";
- * import { CreateAgentParameters } from "@ic-reactor/react/dist/types";
- *
- * // Optional: Define custom agent configuration
- * const agentConfig: CreateAgentParameters = {
- *   host: "https://localhost:8000",
- *   // or
- *   // isLocalEnv: true,
- *   // port: 8000,
- * };
- *
- * export const {
- *   AgentProvider,
- *   useAgent,
- *   useAuthClient,
- *   useAuthState,
- *   useAgentState,
- *   useAgentManager,
- *   useUserPrincipal,
- * } = createAgentContext(agentConfig);
- *
- * // Now you can use the returned hooks in your React components
- *
- * // App.tsx
- * import React from 'react';
- * import { AgentProvider } from './agent';
- *
- * const App = () => (
- *   <AgentProvider>
- *     <Login />
- *     <YourActor />
- *   </AgentProvider>
- * );
- *
- * const Login = () => {
- *  const { login } = useAuthClient()
- *  const principal = useUserPrincipal()
- *
- *  return (
- *    <div>
- *      <button onClick={() => login()}>Login</button>
- *      <p>User: {principal?.toText()}</p>
- *    </div>
- *  )
- * };
+ * Wrap your component tree with `AgentProvider` to provide all child components access to IC agent and authentication hooks.
  *
+ * ```jsx
+ * <AgentProvider>
+ *   <YourComponent />
+ * </AgentProvider>
  * ```
  *
- * This setup allows you to use the agent and authentication hooks within
- * the components wrapped by `AgentProvider`, facilitating interaction
- * with the Internet Computer blockchain.
+ * Inside `YourComponent` or any of its children, you can use the hooks provided through the context to interact with the IC,
+ * manage authentication, and perform other agent-related tasks.
  */
-export declare const createAgentContext: (config?: AgentManagerParameters) => CreateAgentContextReturnType;
+export declare const AgentProvider: import("react").FC<import("../types").AgentProviderProps>;

package/dist/provider/agent.js

@@ -1,124 +1,32 @@
 "use strict";
-var __createBinding = (this && this.__createBinding) || (Object.create ? (function(o, m, k, k2) {
-    if (k2 === undefined) k2 = k;
-    var desc = Object.getOwnPropertyDescriptor(m, k);
-    if (!desc || ("get" in desc ? !m.__esModule : desc.writable || desc.configurable)) {
-      desc = { enumerable: true, get: function() { return m[k]; } };
-    }
-    Object.defineProperty(o, k2, desc);
-}) : (function(o, m, k, k2) {
-    if (k2 === undefined) k2 = k;
-    o[k2] = m[k];
-}));
-var __setModuleDefault = (this && this.__setModuleDefault) || (Object.create ? (function(o, v) {
-    Object.defineProperty(o, "default", { enumerable: true, value: v });
-}) : function(o, v) {
-    o["default"] = v;
-});
-var __importStar = (this && this.__importStar) || function (mod) {
-    if (mod && mod.__esModule) return mod;
-    var result = {};
-    if (mod != null) for (var k in mod) if (k !== "default" && Object.prototype.hasOwnProperty.call(mod, k)) __createBinding(result, mod, k);
-    __setModuleDefault(result, mod);
-    return result;
-};
-var __rest = (this && this.__rest) || function (s, e) {
-    var t = {};
-    for (var p in s) if (Object.prototype.hasOwnProperty.call(s, p) && e.indexOf(p) < 0)
-        t[p] = s[p];
-    if (s != null && typeof Object.getOwnPropertySymbols === "function")
-        for (var i = 0, p = Object.getOwnPropertySymbols(s); i < p.length; i++) {
-            if (e.indexOf(p[i]) < 0 && Object.prototype.propertyIsEnumerable.call(s, p[i]))
-                t[p[i]] = s[p[i]];
-        }
-    return t;
-};
 Object.defineProperty(exports, "__esModule", { value: true });
-exports.createAgentContext = void 0;
-const react_1 = __importStar(require("react"));
-const core_1 = require("@ic-reactor/core");
-const agentHooks_1 = require("../helpers/agentHooks");
-const authHooks_1 = require("../helpers/authHooks");
-const extractAgentContext_1 = require("../helpers/extractAgentContext");
+exports.AgentProvider = void 0;
+const hooks_1 = require("../hooks/agent/hooks");
 /**
- * Creates a React context for managing IC agent and authentication states, providing hooks for interacting with the IC blockchain.
- * This function initializes an `AgentContext` with a set of utilities and hooks based on the provided agent configuration.
+ * `AgentProvider` is a React functional component that serves as a context provider for IC agent and authentication hooks.
+ * It enables any child components to access and use the agent and authentication functionalities seamlessly.
  *
- * @param agentParameters A partial configuration object for the agent manager, allowing customization of the agent's behavior.
+ * The provider encapsulates the logic for initializing and managing an agent manager instance, which is then used to
+ * create various hooks related to agent operations and authentication processes. These hooks are made available to all
+ * child components through the context, facilitating a centralized and efficient way to interact with the Internet Computer (IC) blockchain.
  *
- * @returns An object containing the `AgentProvider` component and various hooks for interacting with the agent and authentication state.
- * The `AgentProvider` component is a React context provider that should wrap your app or components needing access to agent functionalities.
- *
- * Usage:
- * - `AgentProvider`: React component to provide agent context to your application.
- * - `useAgent`, `useAuthClient`, `useAuthState`, `useAgentState`, `useAgentManager`, `useUserPrincipal`: Hooks extracted from the created context for managing agent and authentication state within components.
+ * @param children - Child components that can consume the context.
+ * @param agentManager - An optional `AgentManager` instance to be used by the provider. If not provided, a new instance
+ *                       will be created based on the provided options combined with default configuration.
+ * @param options - Configuration options for the `AgentManager`. These options are merged with any default configurations
+ *                  specified during the context creation and can include custom settings for the agent, such as identity,
+ *                  host URL, etc.
  *
  * @example
- * ```tsx
- * // agent.ts
- * import { createAgentContext } from "@ic-reactor/react";
- * import { CreateAgentParameters } from "@ic-reactor/react/dist/types";
- *
- * // Optional: Define custom agent configuration
- * const agentConfig: CreateAgentParameters = {
- *   host: "https://localhost:8000",
- *   // or
- *   // isLocalEnv: true,
- *   // port: 8000,
- * };
- *
- * export const {
- *   AgentProvider,
- *   useAgent,
- *   useAuthClient,
- *   useAuthState,
- *   useAgentState,
- *   useAgentManager,
- *   useUserPrincipal,
- * } = createAgentContext(agentConfig);
- *
- * // Now you can use the returned hooks in your React components
- *
- * // App.tsx
- * import React from 'react';
- * import { AgentProvider } from './agent';
- *
- * const App = () => (
- *   <AgentProvider>
- *     <Login />
- *     <YourActor />
- *   </AgentProvider>
- * );
- *
- * const Login = () => {
- *  const { login } = useAuthClient()
- *  const principal = useUserPrincipal()
- *
- *  return (
- *    <div>
- *      <button onClick={() => login()}>Login</button>
- *      <p>User: {principal?.toText()}</p>
- *    </div>
- *  )
- * };
+ * Wrap your component tree with `AgentProvider` to provide all child components access to IC agent and authentication hooks.
  *
+ * ```jsx
+ * <AgentProvider>
+ *   <YourComponent />
+ * </AgentProvider>
  * ```
  *
- * This setup allows you to use the agent and authentication hooks within
- * the components wrapped by `AgentProvider`, facilitating interaction
- * with the Internet Computer blockchain.
+ * Inside `YourComponent` or any of its children, you can use the hooks provided through the context to interact with the IC,
+ * manage authentication, and perform other agent-related tasks.
  */
-const createAgentContext = (config = {}) => {
-    const AgentContext = (0, react_1.createContext)(null);
-    const AgentProvider = (_a) => {
-        var { children, agentManager: mybeAgentManager } = _a, options = __rest(_a, ["children", "agentManager"]);
-        const hooks = (0, react_1.useMemo)(() => {
-            const agentManager = mybeAgentManager !== null && mybeAgentManager !== void 0 ? mybeAgentManager : (0, core_1.createAgentManager)(Object.assign(Object.assign({}, options), config));
-            return Object.assign(Object.assign(Object.assign({}, (0, agentHooks_1.agentHooks)(agentManager)), (0, authHooks_1.authHooks)(agentManager)), { agentManager });
-        }, [options]);
-        return (react_1.default.createElement(AgentContext.Provider, { value: hooks }, children));
-    };
-    AgentProvider.displayName = "AgentProvider";
-    return Object.assign({ AgentProvider }, (0, extractAgentContext_1.extractAgentContext)(AgentContext));
-};
-exports.createAgentContext = createAgentContext;
+exports.AgentProvider = hooks_1.AgentHooks.AgentProvider;

package/dist/types.d.ts

@@ -6,6 +6,7 @@ export interface CreateReactorReturnType<A> extends ActorHooksReturnType<A>, Aut
     getAgent: () => HttpAgent;
     getVisitFunction: () => VisitService<A>;
 }
-export * from "./provider/types";
+export * from "./context/types";
 export * from "./helpers/types";
+export * from "./hooks/types";
 export * from "@ic-reactor/core/dist/types";

package/dist/types.js

@@ -14,6 +14,7 @@ var __exportStar = (this && this.__exportStar) || function(m, exports) {
     for (var p in m) if (p !== "default" && !Object.prototype.hasOwnProperty.call(exports, p)) __createBinding(exports, m, p);
 };
 Object.defineProperty(exports, "__esModule", { value: true });
-__exportStar(require("./provider/types"), exports);
+__exportStar(require("./context/types"), exports);
 __exportStar(require("./helpers/types"), exports);
+__exportStar(require("./hooks/types"), exports);
 __exportStar(require("@ic-reactor/core/dist/types"), exports);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ic-reactor/react",
-  "version": "1.0.5",
+  "version": "1.0.7",
   "description": "A React library for interacting with Internet Computer canisters",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",
@@ -35,7 +35,7 @@
     "node": ">=10"
   },
   "dependencies": {
-    "@ic-reactor/core": "^1.0.4",
+    "@ic-reactor/core": "^1.0.6",
     "zustand-utils": "^1.3"
   },
   "peerDependencies": {
@@ -48,5 +48,5 @@
     "react": ">=16.8",
     "zustand": "4.5"
   },
-  "gitHead": "6b8947ab2611bf7af4f0fadaa33a1fa231cfc26b"
+  "gitHead": "bf69ae06def96cd40814a72535325f7c7a8a6b5a"
 }

package/dist/main.d.ts

@@ -1,38 +0,0 @@
-import type { BaseActor, CreateReactorParameters, CreateReactorReturnType } from "./types";
-/**
- * Initializes and configures the reactor environment for interacting with the Internet Computer (IC) blockchain within a React application.
- * It encapsulates the creation of actors, authentication, and agent management, offering a streamlined interface for blockchain interactions.
- *
- * @param config Configuration config for the reactor, including:
- *  - withProcessEnv (optional): Specifies whether to use process environment variables to determine if the environment is local or development. Defaults to false.
- *  - isLocalEnv (optional): Indicates if the current environment is local or development, influencing the agent and actor behavior. Useful for testing or development.
- *  - port (optional): Port number for the local or development environment.
- *  Extends `CreateReactorStoreParameters` which includes HTTP agent config, actor manager config (excluding `agentManager`), and an optional custom agent manager.
- *
- * @returns An object containing various hooks and utilities:
- *  - getAgent: Function to retrieve the configured IC agent.
- *  - getVisitFunction: Function to access the visit function from the actor manager, used for visitor pattern implementations.
- *  - Includes actor, auth, and agent hooks for state management, authentication, and agent operations.
- *
- * @example
- * ```typescript
- * import { createReactor } from "@ic-reactor/react";
- * import type { CreateReactorCoreParameters } from "@ic-reactor/react/dist/types";
- * import { canisterId, idlFactory, yourActor } from "./declaration/yourActor"
- *
- * const config: CreateReactorCoreParameters = {
- *   canisterId,
- *   idlFactory,
- *   host: "https://localhost:8000", // IC network host         |
- *   isLocalEnv: true, // Set true for local network            | one of these
- *   withProcessEnv: true, // Use process.env to determine host |
- *   port: 8000, // Port number for local network               |
- * };
- *
- * export type YourActor = typeof yourActor;
- *
- * export const { useAuthClient, useQueryCall, useUpdateCall } = createReactor<YourActor>(config);
- * // Now you can use the returned hooks in your React components
- * ```
- */
-export declare const createReactor: <A = BaseActor>(config: CreateReactorParameters) => CreateReactorReturnType<A>;

package/dist/main.js

@@ -1,53 +0,0 @@
-"use strict";
-Object.defineProperty(exports, "__esModule", { value: true });
-exports.createReactor = void 0;
-const core_1 = require("@ic-reactor/core");
-const helpers_1 = require("./helpers");
-/**
- * Initializes and configures the reactor environment for interacting with the Internet Computer (IC) blockchain within a React application.
- * It encapsulates the creation of actors, authentication, and agent management, offering a streamlined interface for blockchain interactions.
- *
- * @param config Configuration config for the reactor, including:
- *  - withProcessEnv (optional): Specifies whether to use process environment variables to determine if the environment is local or development. Defaults to false.
- *  - isLocalEnv (optional): Indicates if the current environment is local or development, influencing the agent and actor behavior. Useful for testing or development.
- *  - port (optional): Port number for the local or development environment.
- *  Extends `CreateReactorStoreParameters` which includes HTTP agent config, actor manager config (excluding `agentManager`), and an optional custom agent manager.
- *
- * @returns An object containing various hooks and utilities:
- *  - getAgent: Function to retrieve the configured IC agent.
- *  - getVisitFunction: Function to access the visit function from the actor manager, used for visitor pattern implementations.
- *  - Includes actor, auth, and agent hooks for state management, authentication, and agent operations.
- *
- * @example
- * ```typescript
- * import { createReactor } from "@ic-reactor/react";
- * import type { CreateReactorCoreParameters } from "@ic-reactor/react/dist/types";
- * import { canisterId, idlFactory, yourActor } from "./declaration/yourActor"
- *
- * const config: CreateReactorCoreParameters = {
- *   canisterId,
- *   idlFactory,
- *   host: "https://localhost:8000", // IC network host         |
- *   isLocalEnv: true, // Set true for local network            | one of these
- *   withProcessEnv: true, // Use process.env to determine host |
- *   port: 8000, // Port number for local network               |
- * };
- *
- * export type YourActor = typeof yourActor;
- *
- * export const { useAuthClient, useQueryCall, useUpdateCall } = createReactor<YourActor>(config);
- * // Now you can use the returned hooks in your React components
- * ```
- */
-const createReactor = (config) => {
-    const actorManager = (0, core_1.createReactorStore)(config);
-    const getVisitFunction = () => {
-        return actorManager.visitFunction;
-    };
-    const getAgent = () => {
-        return actorManager.agentManager.getAgent();
-    };
-    return Object.assign(Object.assign(Object.assign({ getAgent,
-        getVisitFunction }, (0, helpers_1.actorHooks)(actorManager)), (0, helpers_1.authHooks)(actorManager.agentManager)), (0, helpers_1.agentHooks)(actorManager.agentManager));
-};
-exports.createReactor = createReactor;

package/dist/provider/ActorProvider.d.ts

@@ -1,27 +0,0 @@
-/// <reference types="react" />
-export declare const ActorHooks: import("./types").CreateActorContextReturnType<import("@ic-reactor/core/dist/types").BaseActor>;
-/**
- * `ActorProvider` is a React functional component that serves as a context provider for IC actor interactions within a React application.
- * It wraps child components, providing them access to actor-specific hooks and functionalities based on the provided canister ID and configuration.
- *
- * Props:
- * - `children`: React Node - The child components that will have access to the actor context.
- * - `canisterId` (optional): string - The Canister ID for actor interactions. If not provided, the default from `createActorContext` is used.
- * - `loadingComponent` (optional): React Node - A component displayed during the loading/fetching state. Defaults to a simple message.
- * - `...restConfig`: Additional configuration options that will be merged with the default configuration provided during context creation.
- *
- * Behavior:
- * - Validates the presence of a `canisterId`. Throws an error if it is missing, ensuring that a valid canister ID is always used for actor operations.
- * - Utilizes `useMemo` to combine the default configuration with the props provided to the `ActorProvider`, optimizing for performance by avoiding unnecessary recalculations.
- * - Employs the `useActor` hook to initiate actor interactions based on the combined configuration, managing states such as `fetching`, `fetchError`, and the actor `hooks`.
- * - Conditionally renders the `loadingComponent` or `fetchError` based on the actor fetching state. Once the actor is ready and no errors are present, it renders the child components, effectively providing them access to the actor context.
- *
- * @example
- * ```jsx
- * <ActorProvider canisterId="your-canister-id">
- *   <YourComponent />
- * </ActorProvider>
- * ```
- * This setup ensures that `YourComponent` and any of its children can interact with the specified IC actor through the context provided by `ActorProvider`.
- */
-export declare const ActorProvider: import("react").FC<import("./types").ActorProviderProps>;

package/dist/provider/ActorProvider.js

@@ -1,30 +0,0 @@
-"use strict";
-Object.defineProperty(exports, "__esModule", { value: true });
-exports.ActorProvider = exports.ActorHooks = void 0;
-const actor_1 = require("./actor");
-exports.ActorHooks = (0, actor_1.createActorContext)();
-/**
- * `ActorProvider` is a React functional component that serves as a context provider for IC actor interactions within a React application.
- * It wraps child components, providing them access to actor-specific hooks and functionalities based on the provided canister ID and configuration.
- *
- * Props:
- * - `children`: React Node - The child components that will have access to the actor context.
- * - `canisterId` (optional): string - The Canister ID for actor interactions. If not provided, the default from `createActorContext` is used.
- * - `loadingComponent` (optional): React Node - A component displayed during the loading/fetching state. Defaults to a simple message.
- * - `...restConfig`: Additional configuration options that will be merged with the default configuration provided during context creation.
- *
- * Behavior:
- * - Validates the presence of a `canisterId`. Throws an error if it is missing, ensuring that a valid canister ID is always used for actor operations.
- * - Utilizes `useMemo` to combine the default configuration with the props provided to the `ActorProvider`, optimizing for performance by avoiding unnecessary recalculations.
- * - Employs the `useActor` hook to initiate actor interactions based on the combined configuration, managing states such as `fetching`, `fetchError`, and the actor `hooks`.
- * - Conditionally renders the `loadingComponent` or `fetchError` based on the actor fetching state. Once the actor is ready and no errors are present, it renders the child components, effectively providing them access to the actor context.
- *
- * @example
- * ```jsx
- * <ActorProvider canisterId="your-canister-id">
- *   <YourComponent />
- * </ActorProvider>
- * ```
- * This setup ensures that `YourComponent` and any of its children can interact with the specified IC actor through the context provided by `ActorProvider`.
- */
-exports.ActorProvider = exports.ActorHooks.ActorProvider;

package/dist/provider/AgentProvider.d.ts

@@ -1,30 +0,0 @@
-/// <reference types="react" />
-export declare const AgentHooks: import("./types").CreateAgentContextReturnType;
-/**
- * `AgentProvider` is a React functional component that serves as a context provider for IC agent and authentication hooks.
- * It enables any child components to access and use the agent and authentication functionalities seamlessly.
- *
- * The provider encapsulates the logic for initializing and managing an agent manager instance, which is then used to
- * create various hooks related to agent operations and authentication processes. These hooks are made available to all
- * child components through the context, facilitating a centralized and efficient way to interact with the Internet Computer (IC) blockchain.
- *
- * @param children - Child components that can consume the context.
- * @param agentManager - An optional `AgentManager` instance to be used by the provider. If not provided, a new instance
- *                       will be created based on the provided options combined with default configuration.
- * @param options - Configuration options for the `AgentManager`. These options are merged with any default configurations
- *                  specified during the context creation and can include custom settings for the agent, such as identity,
- *                  host URL, etc.
- *
- * @example
- * Wrap your component tree with `AgentProvider` to provide all child components access to IC agent and authentication hooks.
- *
- * ```jsx
- * <AgentProvider>
- *   <YourComponent />
- * </AgentProvider>
- * ```
- *
- * Inside `YourComponent` or any of its children, you can use the hooks provided through the context to interact with the IC,
- * manage authentication, and perform other agent-related tasks.
- */
-export declare const AgentProvider: import("react").FC<import("./types").AgentProviderProps>;

package/dist/provider/AgentProvider.js

@@ -1,33 +0,0 @@
-"use strict";
-Object.defineProperty(exports, "__esModule", { value: true });
-exports.AgentProvider = exports.AgentHooks = void 0;
-const agent_1 = require("./agent");
-exports.AgentHooks = (0, agent_1.createAgentContext)();
-/**
- * `AgentProvider` is a React functional component that serves as a context provider for IC agent and authentication hooks.
- * It enables any child components to access and use the agent and authentication functionalities seamlessly.
- *
- * The provider encapsulates the logic for initializing and managing an agent manager instance, which is then used to
- * create various hooks related to agent operations and authentication processes. These hooks are made available to all
- * child components through the context, facilitating a centralized and efficient way to interact with the Internet Computer (IC) blockchain.
- *
- * @param children - Child components that can consume the context.
- * @param agentManager - An optional `AgentManager` instance to be used by the provider. If not provided, a new instance
- *                       will be created based on the provided options combined with default configuration.
- * @param options - Configuration options for the `AgentManager`. These options are merged with any default configurations
- *                  specified during the context creation and can include custom settings for the agent, such as identity,
- *                  host URL, etc.
- *
- * @example
- * Wrap your component tree with `AgentProvider` to provide all child components access to IC agent and authentication hooks.
- *
- * ```jsx
- * <AgentProvider>
- *   <YourComponent />
- * </AgentProvider>
- * ```
- *
- * Inside `YourComponent` or any of its children, you can use the hooks provided through the context to interact with the IC,
- * manage authentication, and perform other agent-related tasks.
- */
-exports.AgentProvider = exports.AgentHooks.AgentProvider;

package/dist/provider/hooks/index.d.ts

@@ -1 +0,0 @@
-export * from "./useActor";

package/dist/provider/index.d.ts

@@ -1,8 +0,0 @@
-/// <reference types="react" />
-import { createActorContext } from "./actor";
-import { createAgentContext } from "./agent";
-export declare const ActorProvider: import("react").FC<import("./types").ActorProviderProps>, useActorState: () => import("../types").UseActorState, useQueryCall: import("../types").UseQueryCall<import("@ic-reactor/core/dist/types").BaseActor>, useUpdateCall: import("../types").UseUpdateCall<import("@ic-reactor/core/dist/types").BaseActor>, useVisitMethod: <M extends string>(functionName: M) => <V extends import("@dfinity/candid/lib/cjs/idl").Visitor<unknown, unknown>>(extractorClass: V, data?: import("@ic-reactor/core/dist/types").VisitorType<V>["data"] | undefined) => ReturnType<V["visitFunc"]>;
-export { createActorContext };
-export declare const AgentProvider: import("react").FC<import("./types").AgentProviderProps>, useAgent: () => import("@dfinity/agent").HttpAgent | undefined, useAuthClient: (args?: import("../types").UseAuthClientParameters | undefined) => import("../types").UseAuthClientReturnType, useAuthState: () => import("@ic-reactor/core/dist/types").AuthState, useAgentState: () => import("@ic-reactor/core/dist/types").AgentState, useAgentManager: (agentContext?: import("react").Context<import("./types").AgentContext | null> | undefined) => import("@ic-reactor/core/dist/types").AgentManager, useUserPrincipal: () => import("@dfinity/principal").Principal | undefined;
-export { createAgentContext };
-export * from "./hooks";

package/dist/provider/index.js

@@ -1,25 +0,0 @@
-"use strict";
-var __createBinding = (this && this.__createBinding) || (Object.create ? (function(o, m, k, k2) {
-    if (k2 === undefined) k2 = k;
-    var desc = Object.getOwnPropertyDescriptor(m, k);
-    if (!desc || ("get" in desc ? !m.__esModule : desc.writable || desc.configurable)) {
-      desc = { enumerable: true, get: function() { return m[k]; } };
-    }
-    Object.defineProperty(o, k2, desc);
-}) : (function(o, m, k, k2) {
-    if (k2 === undefined) k2 = k;
-    o[k2] = m[k];
-}));
-var __exportStar = (this && this.__exportStar) || function(m, exports) {
-    for (var p in m) if (p !== "default" && !Object.prototype.hasOwnProperty.call(exports, p)) __createBinding(exports, m, p);
-};
-var _a, _b;
-Object.defineProperty(exports, "__esModule", { value: true });
-exports.createAgentContext = exports.useUserPrincipal = exports.useAgentManager = exports.useAgentState = exports.useAuthState = exports.useAuthClient = exports.useAgent = exports.AgentProvider = exports.createActorContext = exports.useVisitMethod = exports.useUpdateCall = exports.useQueryCall = exports.useActorState = exports.ActorProvider = void 0;
-const actor_1 = require("./actor");
-Object.defineProperty(exports, "createActorContext", { enumerable: true, get: function () { return actor_1.createActorContext; } });
-const agent_1 = require("./agent");
-Object.defineProperty(exports, "createAgentContext", { enumerable: true, get: function () { return agent_1.createAgentContext; } });
-_a = (0, actor_1.createActorContext)(), exports.ActorProvider = _a.ActorProvider, exports.useActorState = _a.useActorState, exports.useQueryCall = _a.useQueryCall, exports.useUpdateCall = _a.useUpdateCall, exports.useVisitMethod = _a.useVisitMethod;
-_b = (0, agent_1.createAgentContext)(), exports.AgentProvider = _b.AgentProvider, exports.useAgent = _b.useAgent, exports.useAuthClient = _b.useAuthClient, exports.useAuthState = _b.useAuthState, exports.useAgentState = _b.useAgentState, exports.useAgentManager = _b.useAgentManager, exports.useUserPrincipal = _b.useUserPrincipal;
-__exportStar(require("./hooks"), exports);