- Does krystal-sf/ux-bootbox work with Laravel out of the box?
- No. It is a Symfony UX package built around Twig helpers, Stimulus controllers, a Flex recipe, and AssetMapper, and it does not declare a Laravel service provider or package-discovery metadata. Composer can download it in a Laravel project, but nothing will wire up automatically. To use the pattern in Laravel you would need to port it to a Blade component and Vite-based JavaScript.
- How do I install krystal-sf/ux-bootbox in a Symfony application?
- Use Composer and, if the Flex recipe is available, accept it so bundles.php, assets/controllers.json, and Twig paths are configured. Then enable the bundle and import the Stimulus controller through your asset pipeline. Because the GitLab repository may be private or VCS-only, confirm reachability and Packagist availability before relying on composer require in CI.
- Is krystal-sf/ux-bootbox available on Packagist?
- The context does not confirm a Packagist listing; the repository is a company-namespaced GitLab project, which suggests it may be internal or VCS-only. Check Packagist and the repository visibility before adding it to composer.json. If it is not published, you would need a VCS repository entry and credentials for private access.
- How do I show a confirmation dialog before a destructive action in Symfony with this package?
- The package provides Twig helpers and a Stimulus controller for Bootbox confirm flows, so you attach the helper to a button or form and handle the promise-based callback. The exact API is in the package source; the reusable contract is a helper that opens a Bootbox confirm and resolves on OK. In Laravel, the equivalent would be a Blade component that dispatches a browser confirm or custom modal event.
- Can I use krystal-sf/ux-bootbox with Tailwind CSS?
- Bootbox renders Bootstrap modal markup and expects Bootstrap's modal plugin and styling, so using it in a Tailwind front end usually creates visual conflicts or a dual-CSS burden. You can restyle the modal markup, but that largely removes the convenience the package offers. For Tailwind projects, a small custom Alpine or vanilla modal component is often cleaner.
- Which Bootstrap and jQuery versions does this package require?
- Bootbox is a convenience wrapper over the Bootstrap modal plugin and has historically been coupled to jQuery, so the Bootstrap 4 versus 5 and jQuery questions belong to Bootbox itself. The package does not define its own Bootstrap fork; it delegates to Bootbox. Verify the installed bootbox version and its peer dependencies before assuming Bootstrap 5 without jQuery will work.
- Does krystal-sf/ux-bootbox have a Laravel service provider or package discovery?
- No. It follows Symfony UX conventions, registering through config/bundles.php, a DI extension, Twig namespace registration, assets/controllers.json, and a Flex recipe. Laravel discovers packages through extra.laravel.providers, which this package does not declare. That is why composer require alone produces no working modals in a Laravel app.
- Is krystal-sf/ux-bootbox actively maintained and production-ready?
- The available context shows no stars, no dependents, and no public adoption signal, and the GitLab namespace suggests internal tooling. There is no stated security disclosure process or maintenance commitment in the brief. Treat it as a pattern to evaluate rather than a validated dependency, and confirm repository visibility and release history before committing to it.
- What are alternatives to krystal-sf/ux-bootbox for Laravel modals?
- In Laravel, use Blade components with Alpine.js, Livewire, or a small vanilla JavaScript module that calls Bootstrap's modal API or a library like SweetAlert2. If you need server-driven confirmation flows, Livewire actions or Inertia forms are more native than porting a Symfony UX package. The package's value is its Twig helper and Stimulus controller pattern, which is straightforward to reimplement.
- How do I test Bootbox dialogs in a Symfony or Laravel application?
- Browser-level tests with Laravel Dusk, Pest browser, or Symfony Panther can click the trigger and assert the modal text and button behaviour. Unit-testing the JavaScript controller in isolation is also possible with Jest or Vitest by mocking Bootbox. Avoid relying on the package's internal helpers for assertions; test the user-visible dialog contract instead.