This SDK provides React hooks and utilies for making queries and mutations that can take the pain out of building front-end applications for the web or React Native.
They are built as a thin wrapper around TanStack Query for React v5, a powerful, asynchronous state management library. A good understanding of that library will be very helpful while using them. In addition to hooks, there are several helper functions that can be used for cache management and data fetching during server-rendering and in React Server Components.
To get started using React hooks, you will need to inject TanStack query and an SDK instance into your application. Typically, this will be done high up in your React app at the root or layout component. For example:
import { QueryClient, QueryClientProvider } from "@tanstack/react-query";
import { BlueskyCore } from "@speakeasy-api/bluesky";
import { BlueskyProvider } from "@speakeasy-api/bluesky/react-query";
const queryClient = new QueryClient();
const bluesky = new BlueskyCore({
bearer: process.env["BLUESKY_BEARER"] ?? "",
});
// Retries are handled by the underlying SDK.
queryClient.setQueryDefaults(["@speakeasy-api/bluesky"], { retry: false });
queryClient.setMutationDefaults(["@speakeasy-api/bluesky"], { retry: false });
export function App() {
return (
<QueryClientProvider client={queryClient}>
<BlueskyProvider client={bluesky}>
{/* Your app logic starts here */}
</BlueskyProvider>
</QueryClientProvider>
);
}
Query hooks are the basic building block for fetching data. In addition to
request data, they take the same options as the useQuery
hook
from TanStack Query.
import { useActorsGetPreferences } from "@speakeasy-api/bluesky/react-query/actorsGetPreferences.js";
export function Example() {
const { data, error, status } = useActorsGetPreferences();
// Render the UI here...
}
Since the underlying SDK handles request timeouts and retries, there are a few more options provided by the query hooks to control these behaviors.
import { useState } from "react";
import { useActorsGetPreferences } from "@speakeasy-api/bluesky/react-query/actorsGetPreferences.js";
export function ExampleWithOptions() {
const [enabled, setEnabled] = useState(true);
const { data, error, status } = useActorsGetPreferences(
{
// TanStack Query options:
enabled,
staleTime: 60 * 1000, // 1 minute
gcTime: 5 * 60 * 1000, // 5 minutes
// Request options for the underlying API call:
timeoutMs: 1000,
retryCodes: ["5XX"],
retries: {
strategy: "backoff",
backoff: {
initialInterval: 500,
maxInterval: 10 * 1000, // 10 seconds
exponent: 1.5,
maxElapsedTime: 60 * 1000, // 1 minute
},
},
}
);
// Render the UI here...
}
Operations that can have side-effects in this SDK are exposed as mutation hooks.
These can be integrated into HTML forms to submit data to the API. They also
take the same options as the useMutation
hook from TanStack
Query.
import { useActorsPutPreferencesMutation } from "@speakeasy-api/bluesky/react-query/actorsPutPreferences.js";
export function Example() {
const { mutate, status } = useActorsPutPreferencesMutation();
return (
<form
onSubmit={(e) => {
e.preventDefault();
// Read form data here...
mutate({
preferences: [
{
tags: [
"<value>",
],
},
],
});
}}
>
{/* Form fields go here... */}
<button type="submit" disabled={status === "pending"}>Submit</button>
</form>
);
}
Since the underlying SDK handles request timeouts and retries, there are a few more options provided by the mutation hooks to control these behaviors.
import { useActorsPutPreferencesMutation } from "@speakeasy-api/bluesky/react-query/actorsPutPreferences.js";
export function ExampleWithOptions() {
const { mutate, status } = useActorsPutPreferencesMutation({
// TanStack Query options:
networkMode: "online",
gcTime: 5 * 60 * 1000, // 5 minutes
// Request options for the underlying API call:
timeoutMs: 1000,
retryCodes: ["5XX"],
retries: {
strategy: "backoff",
backoff: {
initialInterval: 500,
maxInterval: 10 * 1000, // 10 seconds
exponent: 1.5,
maxElapsedTime: 60 * 1000, // 1 minute
},
},
});
// Render the UI here...
}
In many instances, triggering a mutation hook requires invalidating specific query data currently residing in the TanStack Query's cache. Alongside every query hook there are two functions that help invalidate cached data:
import { useQueryClient } from "@tanstack/react-query";
import { invalidateActorsGetPreferences, invalidateAllActorsGetPreferences } from "@speakeasy-api/bluesky/react-query/actorsGetPreferences.js";
// Replace this with a real mutation
import { useExampleMutation } from "@speakeasy-api/bluesky/react-query/example.js";
export function Example() {
const { queryClient } = useQueryClient();
const { mutate, status } = useExampleMutation();
return (
<form
onSubmit={(e) => {
e.preventDefault();
const formData = new FormData(e.target);
mutate(formData, {
onSuccess: () => {
// Invalidate a single cache entry:
invalidateActorsGetPreferences(queryClient, /* ... arguments ... */);
// OR, invalidate all cache entries for the query targets:
invalidateAllActorsGetPreferences(queryClient);
},
});
}}
>
{/* Form fields go here... */}
<button type="submit" disabled={status === "pending"}>Submit</button>
</form>
);
}
Certain queries may have pagination enabled if the underlying API supports it. In these cases, additional "infinite" query hooks are exposed to help build infinite scrolling and "load more" user interfaces.
Note
The original query hooks will still be available and if you are building a more explicit pagination UI with page numbers and next/previous buttons then those hooks may be more suitable.
import { useSearchActorsInfinite } from "@speakeasy-api/bluesky/react-query/actorsSearch.js";
export function Example() {
const { data, error, status, fetchNextPage, hasNextPage } = useSearchActorsInfinite();
return (
<div>
{/* Render pages here... */}
{hasNextPage ? (
<div>
<button onClick={() => fetchNextPage()}>Load more</button>
</div>
) : null}
</div>
);
}
TanStack Query predates React Suspense and out of the box it does a great job at exposing the lifecycle of asynchronous tasks. However, if you are already using Suspense in your app, the default hooks will not trigger suspense boundaries. This is why the library and, by extension, this SDK also provide equivalent hooks that integrate neatly with React Suspense.
import { QueryClient, QueryClientProvider } from "@tanstack/react-query";
import { ErrorBoundary } from "react-error-boundary";
import { BlueskyCore } from "@speakeasy-api/bluesky";
import { BlueskyProvider } from "@speakeasy-api/bluesky/react-query";
import { useActorsGetPreferencesSuspense } from "@speakeasy-api/bluesky/react-query/actorsGetPreferences.js";
const queryClient = new QueryClient();
const bluesky = new BlueskyCore({
bearer: process.env["BLUESKY_BEARER"] ?? "",
});
export function App() {
return (
<QueryClientProvider client={queryClient}>
<BlueskyProvider client={bluesky}>
<QueryErrorResetBoundary>
{({ reset }) => (
<ErrorBoundary
fallbackRender={({ error, resetErrorBoundary }) => (
<div>
There was an error!{' '}
<Button onClick={() => resetErrorBoundary()}>Try again</Button>
<pre>{error.message}</pre>
</div>
)}
onReset={reset}
>
<React.Suspense fallback={<h1>Loading...</h1>}>
<Example />
</React.Suspense>
</ErrorBoundary>
)}
</QueryErrorResetBoundary>
</BlueskyProvider>
</QueryClientProvider>
);
}
function Example() {
const { data } = useActorsGetPreferencesSuspense();
// Render the UI here...
}
Query hooks are also side-loaded with prefetch helper functions. These functions can be used to fetch data from the API during server-rendering and in React Server Components so that it can be available immediately on page load to any components that use the corresponding hooks:
import {
dehydrate,
HydrationBoundary,
QueryClient,
} from "@tanstack/react-query";
import { BlueskyCore } from "@speakeasy-api/bluesky";
import { prefetchActorsGetPreferences } from "@speakeasy-api/bluesky/react-query/actorsGetPreferences.js";
export default async function Page() {
const queryClient = new QueryClient();
const bluesky = new BlueskyCore({
bearer: process.env["BLUESKY_BEARER"] ?? "",
});
await prefetchActorsGetPreferences(bluesky);
return (
// HydrationBoundary is a Client Component, so hydration will happen there.
<HydrationBoundary state={dehydrate(queryClient)}>
{/* Client components under this point will also have data on page load. */}
</HydrationBoundary>
);
}