Weave Code
Ux Laravel Package
enabel/ux
Enabel UX is a Symfony bundle offering reusable Twig components and utilities for building consistent, maintainable user interfaces. Install it with Composer to streamline common UI patterns across Symfony applications and reduce repetitive template code. Documentation included.
This bundle provides reusable Twig components and utilities for Symfony applications.
Frequently asked questions about Ux
- Is enabel/ux a Laravel package or a Symfony bundle?
- It is a Symfony bundle that ships reusable Twig components, template utilities, and an Enabel Bootstrap-based theme. There is no Blade view, service provider, config publish, or facade, so a plain Composer require gives a Laravel application nothing to render. For Laravel teams the realistic value is the npm theme plus the layout and asset-wiring pattern you can copy into a Blade layout.
- How do I install enabel/ux?
- In a Symfony application you install it with composer require enabel/ux. In Laravel the equivalent step is installing the Enabel Bootstrap theme as an npm dependency and importing it from resources/js/app.js through Vite. Pin the theme version explicitly in package.json instead of letting an automated refresh bump it.
- Can I use the Twig components in Laravel Blade templates?
- Not directly, because Blade does not render Twig. You would need a bridge such as rcrowe/twigbridge, and that is only worth it if your organisation already runs Twig elsewhere in its stack. Otherwise copy the markup patterns into Blade components and keep the bundle out of the app.
- How do I use the Enabel UX Bootstrap theme in Laravel with Vite?
- Add the theme as an npm dependency, then in resources/js/app.js import Bootstrap, import the theme CSS explicitly, and let Vite handle bundling and cache-busting. Since version 2.6.0 the bundle no longer injects CDN CSS/JS into pages, so the host application owns the dependency graph. On Laravel that maps to @vite(...) exactly as importmap('app') does on Symfony.
- Why is window.bootstrap undefined after upgrading to 2.6.0?
- Version 2.6.0 removed the CDN script that defined the global window.bootstrap. Any inline script or Blade partial calling new bootstrap.Modal(...) or bootstrap.Toast(...) now fails at runtime rather than at build time, which makes it the highest-probability regression. Convert those calls to explicit imports from 'bootstrap' in your Vite entrypoint and expose only what you need through a small module.
- Why did my fa-* and fi fi-* icons disappear after the theme 4 upgrade?
- Theme 4 drops Font Awesome and flag-icons from its dependencies, so those class names render nothing until you import the packages yourself. It is a visual-only failure, which means it can ship to production unnoticed. Add the imports to your entrypoint before bumping the theme and re-run visual regression on nav, alerts, and auth screens.
- Does enabel/ux support Laravel 10 or 11, and which PHP versions?
- It has no Laravel version constraints at all because it is not a Laravel package; its composer.json only declares support for Symfony and PHP versions. If you consume just the npm theme, your Laravel and PHP versions are irrelevant to it. Check the repository's composer.json for the current Symfony and PHP support matrix before relying on the Twig side.
- Is enabel/ux production-ready and actively maintained?
- It is MIT licensed, open source, documented, and backed by CI on the Enabel GitHub repository, so the package itself is a reasonable dependency. The technical risk sits mostly with consumer-side breakage on major theme upgrades rather than with the bundle code. Pin versions and read the release notes before every upgrade.
- How should I test an enabel/ux theme upgrade before shipping?
- Audit the codebase for window.bootstrap and bootstrap.* usage in inline script tags and Blade partials, then verify the login and password-reset screens specifically since those were silently double-loading Bootstrap JS. Add Font Awesome and flag-icons imports, pin the theme to ^3.0.2 first, and treat the theme 4 bump as a separate deliberate change with visual regression on iconography. If you use Symfony's importmap:update, remember it ignores version constraints and can pull theme 4 despite ^3.0.2 || ^4.0, so put dependency refreshes behind an approval gate.
- What are the alternatives to enabel/ux for Laravel UI work?
- For Laravel, purpose-built options such as Blade component kits, Tailwind-based UI libraries, Livewire, or Inertia with a Vue or React component library usually fit better than bridging Twig. enabel/ux makes sense mainly if you want Enabel's Bootstrap design system or already run Twig somewhere. Using it purely as a reference for layout and asset wiring is a low-risk middle ground.
Weaver
How can I help you explore Laravel packages today?