Svelte Commerce on Vendure

What works on Vendure today

Known gaps: none recorded.

39 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 Vendure. You need Node.js and a Vendure 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 — swap the stock connector for Vendure’s
npm uninstall @misiki/litekart-connector
npm i @misiki/vendure-connector

# 3 — point it at your Vendure server
echo PUBLIC_VENDURE_API_URL=http://localhost:3000 >> .env

# 4 — run it
npm run dev

Environment variables

The Litekart trio — PUBLIC_LITEKART_API_URL, PUBLIC_LITEKART_STORE_ID, PUBLIC_LITEKART_DOMAIN — is not needed in Vendure mode; /health reports ready as soon as PUBLIC_VENDURE_API_URL is set.

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 Vendure

• Set authOptions.requireVerification to false.
• Allow the storefront’s origin in Vendure’s CORS settings, with credentials. The browser calls PUBLIC_VENDURE_API_URL directly and the connector sends credentials: 'include', so Access-Control-Allow-Origin must echo the exact origin — not * — and Access-Control-Allow-Credentials must be true.

How the integration works

At boot, init in both src/hooks.server.ts and src/hooks.client.ts reads PUBLIC_VENDURE_API_URL and hands it to the connector’s setBaseUrl(). Both hooks matter: the server hook covers server rendering, the client hook covers the browser, which must reach the public Vendure URL in production.

Products, categories (Vendure collections), search, cart, checkout, payment methods, orders, sign-in, profile and addresses all go to Vendure’s Shop API. Checkout attaches the customer before payment — an order cannot reach ArrangingPayment without one — and carries Vendure’s order code out as the order number.

Store identity, menus and plugin toggles come 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”. CMS pages and the blog resolve empty. From connector 2.0.39 the REST paths it once inherited from Litekart are answered by the connector itself.

Two defaults in that static config shape what shoppers see. The search icon in the navigation is hidden (plugins.search.active is false, because autocomplete is Litekart’s Meilisearch), though Vendure’s own search still powers the /products page. And sign-in offers email and password only (loginType is EMAIL): Vendure has no OTP, while email sign-in, sign-up, sign-out and password reset are native GraphQL.

Limitations

• CONNECTORS.md records no known gaps for Vendure; the Vendure guide itself lists what is not implemented yet: wishlist, reviews, coupons, several currencies and regions, Meilisearch faceted search, CMS content and multi-vendor.
• Legal and CMS pages render their layout with empty content.
• Wishlist shows an empty state, and toggling it says “Wishlist is not available on this store”; the cart’s coupon drawer lists none.
• No OTP sign-in: getOtp throws.
• Homepage sections other than the live product list come from the active theme’s static content — the standing rule for themes.
• If the Vendure catalogue has no matching products, product grids render their empty or loading states; the pages still work.
• The Conversational Shopping assistant is Litekart-only; its widget detects the connector and stays hidden without firing requests.

Troubleshooting

Before you rely on it