Weave Code
Twig Components Laravel Package
ibexa/twig-components
Twig Components for Ibexa DXP provides reusable Twig-based UI components and related integration for building and rendering component-driven interfaces within Ibexa projects.
At a glance
Frequently asked questions about Twig Components
- Can I use ibexa/twig-components in a Laravel application?
- No. It is a split-out subpackage of Ibexa DXP and needs the Ibexa kernel, Symfony DI container and Ibexa design engine to boot; the README states you must install Ibexa DXP to use it. There is no Laravel, Blade or Livewire integration, and adding it to a Laravel app would pull in ibexa/* dependencies that cannot run there. For reusable UI in Laravel, use Blade components or view components instead.
- What does ibexa/twig-components actually do?
- It provides dynamic registration and rendering of Twig-based UI components inside Ibexa DXP applications. Components are registered through the Symfony service container and Twig extensions and rendered via Ibexa's design engine and theming layer. The one component clearly surfaced in the release history is ibexa.Table for tabular views. It is not a general-purpose component library.
- How do I install ibexa/twig-components?
- You do not install it standalone. Install Ibexa DXP (typically through the ibexa/dxp meta-package) and this package arrives transitively as part of the platform. The README says plainly that the package is part of Ibexa DXP and that you must install Ibexa DXP to use it. A manual composer require outside a DXP install will not produce a working setup.
- What license does ibexa/twig-components use?
- It ships under the Ibexa Business Use License 2.4, granted by holding a valid Ibexa DXP subscription, or the Ibexa Trial and Test License 2.2 for evaluation access. Composer reports the license as NOASSERTION, so automated license scanners will flag it. Using it is a procurement and legal decision rather than an engineering one, so get sign-off before you build on it.
- Which Ibexa DXP versions support ibexa/twig-components?
- Release lines track the DXP rather than a standalone roadmap: 4.6.x for DXP 4.6 LTS and 5.0.x for DXP 5.0. There is no independent release cadence, and PHP and Twig version constraints follow the DXP baseline, not this package. Match the package line to your DXP line and upgrade them together.
- Does ibexa/twig-components work with standalone Symfony?
- No. Although Ibexa DXP is Symfony-based, the package depends on the Ibexa kernel, the Ibexa design engine and Ibexa-specific Twig extensions that only exist inside a DXP installation. A plain Symfony application cannot boot it, and there is no documented way to use it without the DXP platform. Treat it as a DXP-only artifact.
- Should I require ibexa/twig-components directly in composer.json?
- Prefer consuming it transitively through the ibexa/dxp meta-package. Direct pinning adds a constraint you must bump on every DXP upgrade and creates friction when the platform moves. If a direct constraint is unavoidable, pin to the DXP-matched minor line and treat any change as part of the DXP upgrade, not a separate task.
- How do I render a table using ibexa.Table?
- ibexa.Table is the concrete component surfaced in the 5.0.x release line (IBX-10990), meant for tabular views instead of hand-rolled Twig macros. You register it through the component registration mechanism and render it in templates on an Ibexa DXP 5.0 install with the design engine and theming in place. Package-level API documentation is thin, so rely on DXP documentation and upgrade notes.
- Is ibexa/twig-components actively maintained?
- It is maintained as part of Ibexa DXP, but the split repository itself is quiet: most releases read No significant changes, there is no public issue traffic or dependent ecosystem, and the repo has no community traction. Behavioural changes arrive bundled in DXP upgrade notes rather than here. Treat it as a vendor artifact with no community fallback, not a community package.
- What are the alternatives to ibexa/twig-components for Laravel or non-Ibexa stacks?
- On Laravel, Blade components, anonymous Blade components and view components cover the same reusable-UI use case natively. If you specifically need Twig, a bridge such as spatie/laravel-twig can render Twig templates, but you would build any component registry yourself. There is no port of Ibexa's component registration or ibexa.Table outside DXP, and templates built on these components are not portable if you leave Ibexa.
Weaver
How can I help you explore Laravel packages today?