- What is splash/widgets-bundle?
- splash/widgets-bundle is a Symfony bundle by BadPixxel that provides reusable, configurable dashboard widgets, such as small information boxes rendered into a dashboard region. It centralizes widget registration, configuration, and rendering so you do not repeat view code. Its architecture is built around Symfony bundle conventions, not Laravel.
- Is splash/widgets-bundle a Laravel package?
- No. Despite being evaluated alongside Laravel packages, it ships a Symfony Bundle class, a DI Extension, YAML service configuration, tagged services, and Twig templates. Laravel has no bundle registration or container compiler pass, and it does not use Twig by default. There is no Laravel service provider, facade, config publish tag, or Blade view set.
- Can I composer require splash/widgets-bundle in a Laravel application?
- Composer may resolve the package, but it will not work as a Laravel dependency. There is no service provider to register the bundle, no Blade templates, and no Laravel config publishing. The realistic options are to port the pattern into a first-party Laravel package or run Symfony alongside Laravel, which is disproportionate for dashboard widgets.
- Does splash/widgets-bundle support Laravel 10 or Laravel 11?
- There is no evidence of Laravel support at all, so Laravel 10, 11, or 12 compatibility is not a meaningful question. The package is a Symfony bundle and would need a full reimplementation for Laravel. Do not expect a service provider or Blade integration to appear.
- How do I render splash/widgets-bundle widgets in Laravel Blade?
- You cannot render its widgets directly in Blade because rendering is coupled to Symfony services and Twig templates. Port the widget definition model, registry, and box markup into Blade components, optionally with Livewire for interactivity. If the main value is CSS and box layouts, copy those under the MIT license and skip the PHP.
- What PHP and Symfony versions does splash/widgets-bundle require?
- Check composer.json before doing anything: it will constrain PHP, symfony/framework-bundle, and Twig 2 versus 3. A bundle of this vintage may target Symfony 3 or 4 and PHP 7.x, in which case it will not run unmodified on PHP 8.2+ or Symfony 6+. It may also be config-defined or Doctrine-coupled, which changes extraction effort.
- Is splash/widgets-bundle maintained and safe for production?
- Treat it as high risk for production: one star, zero dependents, a composite score near zero, no issue history, and a bus factor of one. Those are absence-of-evidence signals, not proof of bad code, but there is no production usage or third-party security review to rely on. Use it as a reference implementation, not a dependency.
- What license does splash/widgets-bundle use, and can I fork it?
- It is MIT licensed, so forking, modifying, and vendoring it internally are legally clean. That converts it from an unusable dependency into a usable reference implementation. If you only need the CSS and box layouts, copy those under MIT and avoid the Symfony PHP entirely.
- How much work is it to port splash/widgets-bundle to Laravel?
- For a modest widget system, expect roughly one to two sprints. The clean seams are the widget definition model, the registry, the renderer, and the box markup/CSS, reimplemented as a service provider, config file, and Blade components. Confirm first whether the value is the registry and data model or just the UI, because that changes the estimate from days to weeks.
- Are there better Laravel alternatives for dashboard widgets?
- For Laravel, consider a small first-party package with a widget registry, config file, and Blade components; add Livewire if widgets need interactivity. If you want an existing ecosystem, evaluate Laravel dashboard or admin-panel widget systems such as Filament widgets or Livewire-based dashboards. The right choice depends on whether you need widget composition and registration or only dashboard box UI.