Changelog

What changed in Twilight themes, release by release, starting with the move from Twig to React.

Read this to see what changed in the theme engine and these docs. The newest release is at the top.

React themes launch

15 October 2026

Twilight themes are now built with React. This release replaces the Twig engine, and these docs replace the Twig docs.

Move your theme by the end of November 2026

Every theme must move to React by the end of November 2026. Start with the Quick start, then use the table below to find where each Twig part went.

What changed from Twig

In TwigIn ReactRead
.twig templates in src/viewsReact components and route files in app/Project structure, Routes and pages
Page variables such as product and cartRoute loaders and the typed API clientLoading data, API client
Filters and helpers (money, trans, link)Hooks and components: useMoney, useTranslation, LinkuseMoney, useTranslation, Link
Template hooks: {% hook 'cart:items.start' %}Slots: <HookSlot> and hookRegistryTwig hook names, Hooks and slots
Home components in views/components/homeReact components registered for each blockAdd a home block, Built-in home blocks
Nested locale filesFlat keys in locales/ar.json and locales/en.jsonLanguages and RTL
webpackVite with the twilightReact() pluginVite plugin
salla-* web components and their Tailwind class listThe same components, with React wrappers and their own CSSWeb components, Style web components
The Twilight JS SDKThe same SDK, started by the engine for youSDK
Component hooks (Salla.hooks)UnchangedComponent hooks
Starter theme Raed (Twig)Raed for ReactQuick start

What stayed the same

  • twilight.json still holds your settings, home blocks and features. See twilight.json.
  • The Salla CLI still creates, previews and publishes your theme. See Local development.
  • The Partners Portal, its listing and the review rules. See Partners Portal and Review requirements.
  • Merchants set up the store the same way: the theme editor, the home blocks and the settings work as before.

New in React

  • Pages render on the server first, then run in the browser, so the first view is fast and search engines see full pages. See How it works.
  • Every engine route can be kept as it is or taken over file by file. See Fork a built-in route.
  • Typed data for the store, products, cart and customer. See Data.
  • Tools to build with an AI assistant. See Build with AI.

On this page