Weave Code
Ux Toolkit Laravel Package
symfony/ux-toolkit
Symfony UX Toolkit offers shared utilities and conventions for building Symfony UX packages, simplifying frontend integration and reducing boilerplate when wiring JavaScript components into Symfony applications.
A tool to easily create a design system in your Symfony app with customizable, well-crafted Twig components
Frequently asked questions about Ux Toolkit
- Can I use symfony/ux-toolkit in a Laravel application?
- No, symfony/ux-toolkit is not a Laravel package. It assumes a Symfony application structure, Twig templates, Symfony UX Stimulus controllers, and the ux:install recipe workflow, so it does not map cleanly to Blade, Livewire, Inertia, or Laravel's Vite and service-container conventions. Treat it as Symfony-only unless you are deliberately building an isolated Symfony/Twig sidecar.
- How do I install symfony/ux-toolkit, and does it work with Composer only?
- Installation is via Composer plus Symfony Flex recipes, and the package expects ux:install to wire assets and register Stimulus controllers. A plain Composer require in Laravel will not complete that Symfony-oriented setup. You would need custom glue for asset loading, recipe handling, and controller registration, so do not plan a drop-in install.
- Which Laravel versions are supported by symfony/ux-toolkit?
- There is no Laravel version support because the package targets Symfony, not Laravel. The TPM assessment rates architecture fit as poor for Laravel and integration feasibility as low for a normal Composer dependency. Confirm Symfony, Twig, PHP, and browser requirements upstream before any proof of concept.
- Is symfony/ux-toolkit compatible with Livewire or Inertia?
- Livewire and Inertia are not supported integration targets. The v3.6.0 release fixes many DOM-move, focus, keyboard, modal, and accessibility defects, which shows the components are sensitive to re-rendering and DOM relocation—directly relevant to Livewire morphing and reactive UIs. You would need to test each component's lifecycle behavior manually in an isolated environment.
- What alternatives should Laravel developers consider instead of symfony/ux-toolkit?
- For Laravel-native UI work, compare Flux UI, Livewire components, Filament, or shadcn-vue/react before considering Symfony UX Toolkit. Those options align with Blade, Livewire, Inertia, and Laravel's frontend conventions. Symfony UX Toolkit is a better fit only for Symfony/Twig applications or PHP monorepos that already contain Symfony UX.
- What changed in symfony/ux-toolkit v3.6.0?
- v3.6.0 is a substantial minor release that adds recipes, preview assets, accessibility fixes, and Shadcn alignment work. It also changes recipe install behavior and overwrite handling and fixes the kit linter on Twig 4. No explicit breaking changes are listed, but the breadth of fixes and recipe changes increases upgrade surface.
- Does symfony/ux-toolkit have accessibility and browser testing support?
- The release includes accessibility fixes and new preview assets that can serve as a visual and accessibility regression baseline. Browser tests are sharded and the assessment notes DOM-move, focus, keyboard, and modal fixes. There is no stated accessibility conformance target, so confirm the target and close any gap with your own checks.
- Can I run symfony/ux-toolkit as a sidecar or isolated Twig renderer?
- A sidecar is the only realistic path for a Laravel team, but it is not a drop-in integration. You would run an isolated Symfony/Twig renderer or component layer and build custom glue for recipes, assets, and Stimulus controllers. Run a bounded proof of concept before committing, and do not introduce Symfony UX into the main Laravel application.
- What PHP, Symfony, and Twig versions does symfony/ux-toolkit require?
- The package is built for Symfony with Twig and Stimulus UX, and v3.6.0 updates tooling dependencies and fixes the kit linter on Twig 4. Exact PHP, Symfony, Twig, and browser version support should be confirmed from the package's composer.json and upstream documentation. Do not assume Laravel compatibility from those Symfony-oriented updates.
- Is symfony/ux-toolkit actively maintained and safe for production?
- The package is actively maintained as part of Symfony UX, and v3.6.0 is a substantial minor release. Production safety for a Laravel team is low because of the Symfony/Twig/Stimulus prerequisite and the fast-moving Shadcn alignment cadence. Pin the version, document recipe ownership, and track upstream changes if you proceed.
Weaver
How can I help you explore Laravel packages today?