Weave Code
Theming Bundle Laravel Package
sylius/theming-bundle
Sylius Theming Bundle adds flexible theme support to Sylius storefronts, letting you organize templates, assets, and configuration into reusable themes with inheritance and per-channel theme selection.
Bundle that provides theming feature.
Frequently asked questions about Theming Bundle
- Can I use sylius/theming-bundle in a Laravel application?
- No. It is a Symfony bundle built for Sylius and has no Laravel service provider, facade, Blade integration, or Composer path into a Laravel app. Running it inside Laravel would mean embedding a second framework runtime with two containers and two view layers. That is architectural debt for a presentation-layer concern.
- Is sylius/theming-bundle still maintained?
- No. The repository is archived, with no merged pull requests, no releases, no security response, 21 stars, and 0 dependents. There is no maintainer to escalate to and no upstream to merge from. Abandonment is already realized rather than forecast.
- Does sylius/theming-bundle support Laravel 10 or 11?
- It does not support any Laravel version. The package targets Sylius and Symfony components, Twig, Doctrine, and a Sylius-era PHP constraint set. Installing it alongside a modern Laravel stack is likely to fail Composer resolution or force downgrades of shared Symfony polyfills.
- How do I install sylius/theming-bundle with Composer?
- It is intended for Sylius applications, not Laravel, and the archive status means there is no supported install path today. In a Laravel project, Composer may fail outright or succeed only by downgrading shared Symfony polyfills that Laravel relies on. A successful install is often more dangerous than a failed one because it creates hard-to-diagnose runtime conflicts.
- What Laravel alternatives exist for theme inheritance and asset overriding?
- Laravel already provides the primitives this bundle supplies: Blade view namespaces, the view finder, service providers for registering theme paths, and Vite asset manifests for build-time theme assets. You can implement child-overrides-parent resolution with a custom view finder or view composer. For per-tenant themes, a tenancy package plus request-aware view path resolution is usually cleaner than embedding Symfony.
- Does sylius/theming-bundle work with Blade templates?
- No. The bundle is built around Twig's loader chain and Sylius theme resolution, not Blade's view finder. There is no Blade integration in the package and no community adapter. You would need to reimplement the resolution logic against Laravel's view layer.
- What are the production risks of embedding a Symfony bundle in Laravel?
- The main risks are Composer dependency lock, dual service-container registration, duplicate global helpers, and colliding console commands. These produce intermittent, environment-dependent boot failures that are expensive to reproduce. Because the repository is archived, any vulnerability in theme file resolution or asset serving becomes permanently your organization's responsibility with no patch path.
- How does sylius/theming-bundle implement theme inheritance?
- It layers template inheritance, asset overriding, and per-theme configuration on top of Twig and the Symfony service container. Child themes override parent themes and fall back on a miss, with locator decoration handling resolution precedence. The design is useful as a reference pattern, but the code is tightly coupled to Symfony kernel, DI compiler passes, and Sylius Doctrine entities.
- Can I use sylius/theming-bundle for per-tenant white-label themes in Laravel?
- Not directly. Per-channel theme selection in this bundle is tied to Sylius' channel model and Doctrine-backed theme entities, which do not exist in a Laravel application. Decide first whether themes resolve at request time per tenant or at build time per deploy; build-time themes are a Vite entry-point and asset-manifest problem, while request-time themes need custom Laravel view resolution.
- Should I fork sylius/theming-bundle or reimplement the pattern in Laravel?
- Reimplement the pattern rather than fork the code. The portable ideas are child-overrides-parent fallback, declarative theme location configuration, template-versus-asset precedence rules, and container-level locator decoration. A fork would leave you owning abandoned Symfony-coupled code with zero upstream support, whereas a Laravel-native implementation fits Blade, service providers, and Vite.
Weaver
How can I help you explore Laravel packages today?