Weave Code
Ux Bundle Laravel Package
kibatic/ux-bundle
Kibatic UX Bundle is a Symfony bundle that packages reusable UX helpers and frontend integrations to streamline common interface tasks. Drop it into an existing Symfony app to reduce boilerplate for interactive components and standardize UX behavior across your project.
At a glance
Frequently asked questions about Ux Bundle
- Can I install kibatic/ux-bundle in a Laravel application?
- No. kibatic/ux-bundle is a Symfony bundle that assumes Symfony's bundle registration in config/bundles.php plus a Symfony UX asset pipeline using either AssetMapper or Webpack Encore, and none of that exists in a Laravel application. Laravel has no bundle loader, no bundle introspection commands, and its frontend stack of Blade, Livewire and Vite is architecturally separate from Symfony UX. Running composer require will not produce a working integration because there is no Laravel service provider, facade, or config-publishing step to hook into.
- Is kibatic/ux-bundle a Laravel package or a Symfony bundle?
- It is a Symfony bundle. It packages reusable UX helpers and frontend integrations intended to reduce boilerplate for interactive components and standardize UX behavior across a Symfony project. The README and package metadata make no claim of Laravel support, and the dependency graph points at Symfony components rather than Illuminate packages. Treat it as a Symfony-only dependency.
- What does kibatic/ux-bundle actually provide?
- The stated purpose is a collection of reusable UX helpers and frontend integrations that cut boilerplate for interactive components in a Symfony app. It operates at the rendering and asset layer rather than the domain or data layer, so its blast radius is limited to UI conveniences. Because the package is small, verify in the source whether it adds genuine functionality or thinly re-exports upstream Symfony UX features such as Turbo, Stimulus and Twig components before assuming it fills a gap.
- Does kibatic/ux-bundle work with Livewire, Inertia, or Blade components?
- No. Livewire, Inertia and Blade are Laravel-side technologies, while kibatic/ux-bundle targets Twig templates and Symfony UX controllers and Stimulus behavior. There is no Blade directive, Livewire component, or Inertia adapter in the package. If you want the ideas rather than the dependency, read the source and reimplement the helpers as Blade components or Livewire traits.
- Does kibatic/ux-bundle support Laravel 11 or Laravel 12?
- There is no Laravel support in any version, including Laravel 11 and Laravel 12. Support is expressed against Symfony versions and the Symfony UX ecosystem, not against Illuminate framework releases. Do not plan a Laravel upgrade path around this package, because no such path exists without a full port.
- How do I install kibatic/ux-bundle in a Symfony project?
- The mechanics are standard Symfony: run composer require kibatic/ux-bundle, accept the Flex recipe if one is published, otherwise register the bundle manually in config/bundles.php. Then wire the asset pipeline through AssetMapper or Webpack Encore and run the usual console commands to validate container and configuration. Pin an exact version, read the diff, and confirm the release you are installing is a real published tag with a changelog before going further.
- Is kibatic/ux-bundle actively maintained and production ready?
- The adoption signals are weak: a single maintainer, zero stars, zero dependents, and no issue history to inspect. A release dated 2026-06-11 should be verified as a genuine tag rather than a pre-release or metadata artifact before it is used as a stability marker. The risk is concentrated in sustainability and framework coupling rather than code quality, since a small rendering-layer package cannot break auth, payments, or persistence if it fails.
- Which Symfony versions does kibatic/ux-bundle support?
- The overview does not state an explicit Symfony version support window, so read the constraints in composer.json before committing. UX bundles typically track Symfony minors closely, which means a stalled maintainer can effectively pin your application to an unsupported Symfony release and turn into a security-patching and compliance problem over time. Pin an exact version and add dependency monitoring so a stalled release surfaces early.
- What should Laravel developers use instead of kibatic/ux-bundle?
- On Laravel, the equivalent layer is built from Blade components, Livewire or Alpine.js for interactivity, and Vite for assets, optionally paired with packages such as Livewire, Volt, or Inertia depending on your rendering model. For a Symfony estate, the natural comparison is upstream Symfony UX itself, meaning Turbo, Stimulus, and Twig components. If kibatic/ux-bundle is only re-exporting those features, the upstream packages are the safer and better-supported choice.
- Can I port kibatic/ux-bundle to Laravel, or should I build my own helpers?
- A port means extracting Twig helpers into Blade directives or rebuilding the opinionated defaults from scratch, at which point you are no longer adopting the package in any meaningful sense. Because it is MIT licensed, forking is cheap in licence terms but expensive in engineering terms, since you inherit a permanent upgrade-cadence obligation for a thin convenience layer. The pragmatic move is to treat the repository as a pattern reference and write a small internal helper package you own, then compare that 24-month cost against maintaining a fork.
Weaver
How can I help you explore Laravel packages today?