- Is krystal-sf/ux-extras a Laravel package?
- No. The vendor namespace and upstream description indicate a Symfony UX bundle built for Krystal Symfony projects, with Twig components, Stimulus controllers and Symfony bundle wiring. It has been catalogued alongside Laravel packages, but it does not ship a Laravel service provider, Blade components or Composer auto-discovery for Laravel. Treat it as a Symfony package that may contain portable front-end assets, not as a Laravel dependency.
- Can I install krystal-sf/ux-extras in a Laravel app with Composer?
- You could technically require it, but installing it will pull transitive Symfony UX dependencies that assume a Symfony kernel and asset pipeline. You will not get a Laravel service provider or config publish tag, so there is dependency drag with no functional payoff. The realistic approach is to audit the repository and port the parts you need rather than run composer require.
- What can I reuse from krystal-sf/ux-extras in a Laravel project?
- The portable layers are the Stimulus controllers, CSS and design tokens, and the Twig markup as a reference implementation to port by hand. Bundle wiring and DI configuration are not applicable to Laravel. Everything server-side is effectively documentation rather than reusable code. The README and component conventions can still be valuable as a design reference.
- Does krystal-sf/ux-extras support Laravel 10 or 11?
- Laravel version support is not really the right frame because the package is a Symfony UX bundle with no Laravel service provider or Blade components. There is no tagged Laravel compatibility matrix to check. You would instead validate the extracted JavaScript and CSS against your Vite build and confirm PHP or Symfony constraints only for any code you choose to port.
- How do I use krystal-sf/ux-extras Stimulus controllers with Vite in Laravel?
- Stimulus controllers are the most portable layer. Copy them into resources/js and register them through a Stimulus bootstrap so Vite can bundle them. They are JavaScript and framework-agnostic, so they do not depend on Symfony at runtime. Do not expect the Symfony bundle wiring or AssetMapper configuration to carry over, and check each controller for third-party dependencies first.
- What are the hard dependencies of krystal-sf/ux-extras?
- The context points to symfony/ux-twig-component, symfony/stimulus-bundle and AssetMapper as likely dependencies, several of which transitively assume a Symfony kernel. Version constraints are not confirmed in the provided material. Before any spend, verify the exact dependency list, PHP and Symfony version constraints, and whether a tagged release exists at all.
- Is krystal-sf/ux-extras tested and safe for production?
- The adoption signals are weak: zero stars, zero dependents, an opportunity score of 27.56 and no visible release cadence. That means no ecosystem validation and no one stress-testing the code against new framework releases. The open unknowns include license terms, version constraints, whether a tagged release exists, and the last commit date. Audit those before any production commitment.
- What license does krystal-sf/ux-extras use, and can I fork it?
- The provided material does not state a license, so confirm the terms before any commercial use. You need explicit permission to reuse internally, modify the code and redistribute a fork. Ask the vendor or maintainer directly. Without clear terms, treat the package as reference-only.
- How do I port Twig components from krystal-sf/ux-extras to Laravel Blade?
- Treat the Twig markup and form themes as a reference implementation and rewrite them as Blade components. Carry CSS and design tokens across as a vendored stylesheet in your Vite pipeline. Reuse Stimulus controllers by registering them in your resources/js bootstrap. There is no shared abstraction layer or automated bridge, so plan on a manual, component-by-component port.
- Is krystal-sf/ux-extras maintained, and are there better alternatives?
- There is no visible release cadence or ecosystem activity, so it may be internal or orphan code provided as-is. Ask whether Krystal is willing to support it or whether it is strictly read-only. The context does not name specific Laravel alternatives. For build versus borrow, adopt third-party widgets directly if the package only wraps them thinly.