StoreKitdocs
SDK

Other frameworks

React, Astro, and Svelte adapters are coming. What you can use today.

The Storefront API is universal, and dedicated SDK adapters are rolling out per framework.

Status

Next.js — Available

Full server + browser integration. See the Next.js adapter.

React (Vite/CRA) — Coming soon

A standalone adapter with a lightweight server proxy and the same hooks.

Astro — Coming soon

Server endpoints + islands integration.

Svelte / SvelteKit — Coming soon

Server hooks + stores.

Want updates?

Watch the repository for adapter releases.

What you can build today

You don't have to wait — the core client works in any JavaScript runtime right now. The pattern that keeps your store key secret is the same one the Next.js adapter automates:

Create a server client with your store key, anywhere your framework runs server code (Astro endpoints, SvelteKit +server.ts, a Vite app's API routes, an Express/Hono backend).

import { createStorefrontClient } from "@usestorekit/sdk";

export const client = createStorefrontClient({
  baseURL: process.env.STOREFRONT_API_URL!,
  storeKey: process.env.STOREFRONT_STORE_KEY!,
});

Expose a thin proxy on your own origin that forwards to the client and attaches the customer's session (from a cookie you set on login). The browser calls this proxy — never the API directly.

Call the proxy from the browser. Read data, add to cart, and log in through your own endpoints. Format prices with formatMoney() from @usestorekit/sdk.

When the dedicated adapter for your framework ships, you'll be able to drop the hand-rolled proxy and use the same ergonomic API as the Next.js adapter.

The browser hooks work in any React app

The @usestorekit/sdk/react hooks (useCart, useSession, usePaymentConfirmation) aren't Next-specific — they only need a same-origin proxy mounted at basePath. If your React framework can serve that proxy, you can use the hooks today by pointing createStorekitClient({ basePath }) at it.

On this page