Svelte Commerce on Magento

What works on Magento today

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

26 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 Magento. You need Node.js and a Magento 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/magento-connector

# 3 — point it at your Magento store
echo PUBLIC_MAGENTO_API_URL=https://your-store.example.com >> .env
echo PUBLIC_MAGENTO_ACCESS_TOKEN=... >> .env

# 4 — run it
npm run dev

Environment variables

init.ts hands the connector every PUBLIC_MAGENTO_* variable that is set, camel-cased. The guide also lists PUBLIC_MAGENTO_API_KEY, PUBLIC_MAGENTO_API_SECRET, PUBLIC_MAGENTO_ACCESS_KEY and PUBLIC_MAGENTO_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 Magento

• Since Magento 2.4.4, an integration token works as a standalone bearer token only once you enable Stores › Configuration › Services › OAuth › Consumer Settings › “Allow OAuth Access Tokens to be used as standalone Bearer tokens” (bin/magento config:set oauth/consumer/enable_integration_as_bearer 1). Without it, every admin route returns 401.
• Let the storefront’s origin make cross-origin requests to Magento (CORS): in production the browser calls PUBLIC_MAGENTO_API_URL directly, not only the server.

How the integration works

The connector speaks Magento’s REST API under /rest/V1, scoped to a store view when one is set. It picks a token per call: the shopper’s customer token for their own cart and account, the admin or integration token for catalogue, CMS, orders and coupons — which have no shopper-level access — and no token at all for guest carts and search.

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_MAGENTO_* 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 — Magento_Review ships no webapi.xml, so there is no REST surface to call.
• Wishlist: not wired — Magento_Wishlist ships no webapi.xml either.
• Pages that depend on a service that is not wired render their empty state rather than failing.
• The admin or integration token the connector needs for the catalogue comes from PUBLIC_MAGENTO_ACCESS_TOKEN. SvelteKit sends PUBLIC_ variables to the browser, so every visitor to the store can read that token and use whatever access the integration has.
• 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