Weave Code
Theme Bundle Laravel Package
integrated/theme-bundle
Integrated Theme Bundle provides theme management for PHP applications, letting you organize, configure, and switch between themes with integrated asset and template support. It helps keep theme files structured and apply consistent styling across your app.
Provides website theme support, which makes it easy to share themes between websites or use a multi-site in your application
Frequently asked questions about Theme Bundle
- Is integrated/theme-bundle a Laravel package?
- No. It is a Symfony bundle, despite often being evaluated for Laravel projects. It ships no Laravel ServiceProvider, facade, Blade integration, or config/theme.php. In a Laravel application it will not register views or assets after composer require.
- Can I install integrated/theme-bundle in a Laravel application with Composer?
- You can add it via Composer, but it will not integrate with Laravel's container, view finder, or asset pipeline. It relies on Symfony's dependency injection container, event dispatcher, and Twig loader. Making it work would require an adapter layer proxying a Symfony kernel, which is disproportionate engineering for a theming concern. A clean port is the more realistic path.
- Does integrated/theme-bundle support Laravel Blade templates?
- No. The package is built around Symfony's Twig loader and template path registration, not Laravel's Blade compiler or view finder. It provides no Blade directives, view namespaces, or Laravel view resolution. For Blade workflows you would need to reimplement theme path resolution against Laravel's view finder.
- How does theme switching work in integrated/theme-bundle?
- It uses a theme registry and resolver with a per-request selection step, likely through a Symfony request subscriber. Themes are named bundles with their own views, assets, and configuration, and a fallback default can be configured. The selection mechanism, whether host, path, cookie, user, or locale, should be checked in the source for extensibility.
- What Laravel versions does integrated/theme-bundle support?
- None officially. The package targets Symfony and declares Symfony and PHP constraints, not Laravel version constraints. It has no illuminate/support, illuminate/view, or laravel/framework dependency. Treat any Laravel compatibility as something you would build, not something the package provides.
- Is integrated/theme-bundle maintained and safe for production?
- The project shows one star, zero dependents, a composite score around 0.135, and effectively a single maintainer. There is no observable production use, issue traffic, or compatibility pressure. MIT licensing limits legal risk but not engineering risk. For production Laravel work, a small in-house theme resolver or a maintained Laravel theming package is safer.
- What are alternatives to integrated/theme-bundle for Laravel theming?
- For Laravel, consider maintained theming packages that integrate with Blade and Laravel's view finder, or build a lightweight theme registry using config and middleware. If you only need per-tenant layouts, a config flag plus namespaced Blade views may be enough. The package's registry and resolver pattern remains a useful reference even if you do not adopt it.
- How hard is it to port integrated/theme-bundle to Laravel?
- The core is small: a config tree, a theme registry or manager service, a request subscriber for selection, and a compiler pass for template paths. Reimplementing that shape against Laravel's config, middleware, and view finder is roughly 100 to 200 lines. A time-boxed spike reading those files should give a reliable estimate.
- Does integrated/theme-bundle handle assets and per-theme configuration?
- Yes conceptually: each theme bundle keeps its own views, assets, and configuration self-contained, with an override hierarchy for customization. In Symfony that asset resolution is wired through the bundle's container and Twig paths. In Laravel you would need to map those asset paths to public disk or asset publishing and register view namespaces yourself.
- Should I use integrated/theme-bundle for a multi-tenant or white-label Laravel app?
- Only as a reference model, not as a dependency. It fits server-rendered template apps with genuine multi-site or white-label needs, but not JSON APIs, SPAs, or heavy Inertia or Livewire apps where theming belongs in the build layer. For a Laravel shop, inventory your current theming approach, then port the cleaner parts of this package's registry and resolver pattern.
Weaver
How can I help you explore Laravel packages today?