Aditya Mathur
Bluesky Logo

hi 👋

Like icon

4

Reply icon

Reply

View on Bluesky

View on Bluesky

Introduction

bsky-react-post allows you to embed posts in your React application when using Next.js, Vite, and more. Posts can be rendered statically, preventing the need to include an iframe and additional client-side JavaScript.

You can try it out in the live playground.

This library is fully compatible with React Server Components. Learn more.

Installation

Install bsky-react-post using your package manager of choice:

npm install bsky-react-post

Now follow the usage instructions for your framework or builder:

Important: Before going to production, we recommend enabling cache for the Bluesky API as server IPs might get rate limited by Bluesky.

Choosing a theme

The prefers-color-scheme CSS media feature is used to select the theme of the post.

Toggling theme manually

The closest data-theme attribute on a parent element can determine the theme of the post. You can set it to light or dark, like so:

<div data-theme="dark">
  <Post handle="adima7.bsky.social" id="3laq6uzwjbc2t" />
</div>

Alternatively, a parent with the class light or dark will also work:

<div className="dark">
  <Post handle="adima7.bsky.social" id="3laq6uzwjbc2t" />
</div>

Updating the theme

In CSS Modules, you can use the :global selector to update the CSS variables used by themes:

.my-class :global(.bsky-react-post-theme) {
  --post-body-font-size: 1rem;
}

For Global CSS the usage of :global is not necessary.

Enabling cache for the Bluesky API

Rendering posts requires making a call to Bluesky's syndication API. Getting rate limited by that API is very hard but it's possible if you're relying only on the endpoint we provide for SWR (bsky-react-post.rhinobase.io/api/post) as the IPs of the server are making many requests to the syndication API. This also applies to RSC where the API endpoint is not required but the server is still making the request from the same IP.

To prevent this, you can use a db like Redis to cache the posts. If you're using Next.js then using unstable_cache works too.