- Does krystal-sf/ux-menus work in a Laravel application?
- No, not out of the box. It is a Symfony UX component built on Twig templates, Symfony dependency injection tags, and a Symfony asset pipeline, so none of its wiring maps directly onto Laravel. There is no Laravel service provider or package auto-discovery, and rendering happens in Twig rather than Blade. You can port the menu data model into Laravel idioms, but treat that as a rewrite of the integration layer rather than a simple composer require.
- How do I install krystal-sf/ux-menus with Composer?
- You can pull it in via Composer from its GitLab repository, but in a Laravel app installation alone will not give you a working menu system. You would still need to register the Symfony bundle, tag services, and wire Twig and front-end assets manually. For Laravel, the practical route is to vendor or fork the source and expose it through your own service provider.
- Is krystal-sf/ux-menus compatible with Laravel 10 or Laravel 11?
- There is no stated Laravel support matrix, because the package targets Symfony UX rather than Laravel. Compatibility with Laravel 10 or 11 is therefore not claimed and would depend entirely on a port you write and maintain yourself. Check the repository for its PHP and Symfony version constraints before planning anything.
- What does tagged menus mean in krystal-sf/ux-menus?
- The name most likely refers to menu items collected through Symfony dependency injection tags and compiled into a menu tree by a compiler pass. Laravel's container also supports tag and tagged, so the concept is portable even though the package's own wiring is not. Confirm this by reading the source, since the package description does not define its API surface.
- Can I render krystal-sf/ux-menus menus in Blade templates?
- Not directly. The package renders through Twig, and its front-end behaviour likely depends on Stimulus controllers registered in a Symfony asset pipeline. To use it in Blade you would extract the menu structure and output it through a Blade component or view composer. That is a custom implementation, not a supported integration.
- What are the Laravel alternatives to krystal-sf/ux-menus?
- Established Laravel packages such as spatie/laravel-menu and lavary/laravel-menu cover nested menus, active-state handling, and Blade rendering with no porting effort. They are built and maintained for Laravel and integrate through service providers and facades. Evaluate them first unless the Symfony package offers a feature you genuinely cannot reproduce.
- What dependencies does krystal-sf/ux-menus require?
- Expect Symfony UX dependencies, most likely Twig, Symfony dependency injection, and a Symfony asset strategy such as AssetMapper or Encore with Stimulus. The repository metadata does not enumerate hard dependencies, so inspect its composer.json before making assumptions. Every Symfony-specific dependency becomes a rework item in a Laravel application.
- Is krystal-sf/ux-menus safe to use in production?
- It has no published adoption signals, no dependents, and no visible changelog, so it should be treated as unproven internal tooling. License terms and the security disclosure process are not clear from the available metadata and must be confirmed before vendoring any code. For production Laravel work, a maintained Laravel-native alternative carries far less risk.
- How do I port krystal-sf/ux-menus to Laravel?
- Vendor the source into your app or a private path repository, retain the upstream Git history, and strip out the Symfony bundle and Twig wiring. Re-register menu items through a Laravel service provider using container tags, then render the tree with a Blade component. The domain model is small, so this is typically an afternoon to a week of work depending on the feature surface you need.
- Is krystal-sf/ux-menus actively maintained and tested?
- The repository shows zero stars and zero dependents, which suggests a single-organisation project rather than a community library. Test coverage, release tagging, and commit cadence are not described in the available metadata. Check open merge requests and tagged releases before depending on it for anything long-lived.