Svelte Commerce on Swell

What works on Swell today

Known gaps: review, wishlist, vendor, state — each is explained under Limitations below.

23 of 43 services wired, read from CONNECTORS.md on 21 September 2026, where the package version is recorded too; npm may carry a newer patch. Coverage is traced by a script in the Svelte Commerce repository: a service counts as wired only if it transitively issues an HTTP request, or delegates to one that does. It is not hand-asserted. Some services are Litekart-native concepts with no equivalent elsewhere (reels, deals, chat, gallery, popularity, demo-request, feedback, plugins, banner). They stay documented placeholders on every connector and are excluded from known gaps.

Quick start

From nothing to a Svelte Commerce storefront reading Swell. You need Node.js and a Swell to point it at; the storefront holds no data of its own.

# 1 — get the storefront
git clone https://github.com/itswadesh/svelte-commerce
cd svelte-commerce

# 2 — one connector at a time: remove the two the storefront ships with, add this one
npm uninstall @misiki/litekart-connector @misiki/vendure-connector
npm i @misiki/swell-connector

# 3 — point it at your Swell store
echo PUBLIC_SWELL_API_URL=https://your-store.swell.store >> .env
echo PUBLIC_SWELL_API_KEY=pk_... >> .env

# 4 — run it
npm run dev

Environment variables

init.ts hands the connector every PUBLIC_SWELL_* variable that is set, camel-cased. The guide also lists PUBLIC_SWELL_ACCESS_TOKEN, PUBLIC_SWELL_ACCESS_KEY and PUBLIC_SWELL_CHANNEL_ID; the connector’s source does not read them.

Every variable here begins PUBLIC_, and SvelteKit sends PUBLIC_ variables to the browser: treat each value you set as published.

What to set up on Swell

• For cash on delivery, add a manual payment method named cod in Swell’s payment settings; without one, the storefront’s cash-on-delivery option is refused.
• Let the storefront’s origin make cross-origin requests to Swell (CORS): in production the browser calls PUBLIC_SWELL_API_URL directly, not only the server.

How the integration works

Swell has two APIs. The storefront API takes the public key alone as HTTP Basic, and it is the one the storefront calls. The Backend API takes the store ID and secret key, and the connector refuses to call it from a browser.

Installing the package is the whole switch. vite.config.ts resolves whichever @misiki/*-connector is installed, and src/lib/core/connectors/init.ts hands it every PUBLIC_SWELL_* variable that is set, camel-cased, at boot — in the server hook for server rendering and in the client hook for the browser, which must reach the same URL in production.

There is no Litekart API behind the storefront here, so store identity — name, logo, currency, menus, plugin toggles, theme colours — comes from src/lib/core/connectors/default-store.json merged under the default export of kitcommerce.config.ts. Until you override it, the store is called “Test”. Any Litekart REST path the connector still inherits is answered from that local data, or resolved empty, rather than requested.

Limitations

• Reviews: not wired.
• Wishlist: not wired.
• Vendors: not wired.
• States and regions: not wired.
• Pages that depend on a service that is not wired render their empty state rather than failing.
• Setting PUBLIC_SWELL_API_SECRET would put Swell’s secret key in every visitor’s browser: SvelteKit sends PUBLIC_ variables to the browser, even though the connector only calls the Backend API from the server.
• Homepage sections other than the live product list come from the active theme’s static content — the standing rule for themes.
• The Conversational Shopping assistant is Litekart-only; its widget stays hidden when another connector is active.

Troubleshooting

Before you rely on it