@unifold/react-provider 0.1.70 → 0.1.71-beta.1

package/dist/index.d.mts

@@ -9,11 +9,17 @@ interface UnifoldProviderProps {
     children: React.ReactNode;
     publishableKey: string;
     /**
-     * Bring your own TanStack QueryClient. When provided, UnifoldProvider will
-     * use this client and will NOT wrap children in a QueryClientProvider
-     * (it assumes one already exists higher in the tree).
+     * Bring your own TanStack QueryClient. When provided, UnifoldProvider uses
+     * this client instance (so Unifold's queries share the host app's cache /
+     * devtools and no second client is created). When omitted, an internal
+     * QueryClient is created automatically.
      *
-     * When omitted, an internal QueryClient is created automatically.
+     * Either way, UnifoldProvider ALWAYS renders its own QueryClientProvider with
+     * the resolved client. A `QueryClient` instance is not the same as a mounted
+     * `QueryClientProvider`, and Unifold UI (e.g. the deposit modal) frequently
+     * renders in a detached React root with no ancestor provider — so it must
+     * provide the client itself to avoid "No QueryClient set" crashes. Wrapping
+     * with the same instance the host already provides is a harmless no-op.
      */
     queryClient?: QueryClient;
 }

package/dist/index.d.ts

@@ -9,11 +9,17 @@ interface UnifoldProviderProps {
     children: React.ReactNode;
     publishableKey: string;
     /**
-     * Bring your own TanStack QueryClient. When provided, UnifoldProvider will
-     * use this client and will NOT wrap children in a QueryClientProvider
-     * (it assumes one already exists higher in the tree).
+     * Bring your own TanStack QueryClient. When provided, UnifoldProvider uses
+     * this client instance (so Unifold's queries share the host app's cache /
+     * devtools and no second client is created). When omitted, an internal
+     * QueryClient is created automatically.
      *
-     * When omitted, an internal QueryClient is created automatically.
+     * Either way, UnifoldProvider ALWAYS renders its own QueryClientProvider with
+     * the resolved client. A `QueryClient` instance is not the same as a mounted
+     * `QueryClientProvider`, and Unifold UI (e.g. the deposit modal) frequently
+     * renders in a detached React root with no ancestor provider — so it must
+     * provide the client itself to avoid "No QueryClient set" crashes. Wrapping
+     * with the same instance the host already provides is a harmless no-op.
      */
     queryClient?: QueryClient;
 }

package/dist/index.js

@@ -70,9 +70,6 @@ function UnifoldProvider({
     [publishableKey]
   );
   const content = /* @__PURE__ */ (0, import_jsx_runtime.jsx)(UnifoldContext.Provider, { value: contextValue, children });
-  if (externalQueryClient) {
-    return content;
-  }
   return /* @__PURE__ */ (0, import_jsx_runtime.jsx)(import_react_query.QueryClientProvider, { client: queryClient, children: content });
 }
 function useUnifold() {

package/dist/index.mjs

@@ -43,9 +43,6 @@ function UnifoldProvider({
     [publishableKey]
   );
   const content = /* @__PURE__ */ jsx(UnifoldContext.Provider, { value: contextValue, children });
-  if (externalQueryClient) {
-    return content;
-  }
   return /* @__PURE__ */ jsx(QueryClientProvider, { client: queryClient, children: content });
 }
 function useUnifold() {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@unifold/react-provider",
-  "version": "0.1.70",
+  "version": "0.1.71-beta.1",
   "description": "Unifold React Provider - Core provider and context for Unifold React SDKs",
   "main": "./dist/index.js",
   "module": "./dist/index.mjs",