- Is friendsofvictoire/tab-widget a Laravel package or a Symfony bundle?
- Despite the Composer name, the repository is FriendsOfVictoire/WidgetTabBundle, and the Bundle suffix plus FriendsOf naming point to a Symfony bundle. It has no Laravel service provider, no Illuminate dependencies, and no extra.laravel block. Treat it as Symfony-targeted code, not a native Laravel package.
- How do I install friendsofvictoire/tab-widget in a Laravel application?
- You can try composer require friendsofvictoire/tab-widget, but resolution will likely fail because the package's constraints target PHP 5.5–7.0 and Symfony 2.7–3.0. Using --ignore-platform-reqs only postpones runtime failures. There is no documented Laravel installation path or service provider to register.
- Does friendsofvictoire/tab-widget support Laravel 10 or Laravel 11?
- No. The last release was in August 2016, and its constraint set is from the PHP 5.5–7.0 and Symfony 2.7–3.0 era. Laravel 10 and 11 require PHP 8.1+, so Composer dependency resolution will almost certainly fail. Even a forced install gives you Symfony container and Twig assumptions Laravel cannot satisfy.
- Can I render friendsofvictoire/tab-widget tabs with Blade?
- Not directly. The bundle is built around Symfony's templating layer, typically Twig, and there is no Blade integration or view namespace for Laravel. You would have to rewrite the rendering layer as Blade components or Livewire. The package does not provide usable Blade directives or views out of the box.
- Is friendsofvictoire/tab-widget abandoned or actively maintained?
- It is effectively abandoned: last release 2016-08-22, 2 stars, 0 dependents, and no maintainer activity. Zero dependents means no one has exercised it in a real dependency graph even in Symfony. There is also no security response path, so Laravel's composer audit would likely flag it.
- What are good Laravel alternatives for tabbed widgets or admin panels?
- For Laravel admin and dashboard tabs, use first-party Blade components, Livewire components, or Filament. These are maintained, PHP 8.1+ compatible, and integrate with Laravel's container and view layer. They cover the same presentational need without dragging in a second framework runtime.
- How do I define tabs and active state if I reuse the tab-widget code?
- The bundle's tab logic is mostly array shaping plus render wiring, so a Laravel reimplementation can define tabs as a PHP array or config file. Active-state handling would be a simple request parameter or Livewire property. Because the original wiring is Symfony-specific, expect to rewrite rather than copy the integration layer.
- What PHP and Symfony versions does friendsofvictoire/tab-widget require?
- Its 2016 release places it in the PHP 5.5–7.0 and Symfony 2.7–3.0 range. It predates modern PHP 8 syntax and Laravel's PHP 8.1+ baseline. That mismatch is the main reason Composer resolution fails on current Laravel projects.
- Should I use friendsofvictoire/tab-widget in production?
- No. The abandoned status, zero adoption, ecosystem mismatch, and lack of security maintenance make it unsuitable for production. The build-vs-adopt tradeoff favors writing a few hundred lines of Blade or Livewire code. Keep the package only as a design reference if you need tab UI ideas.
- Can I extract the friendsofvictoire/tab-widget tab logic into Laravel without installing it?
- Possibly, if the core logic is framework-agnostic PHP, but the repository is Symfony bundle code and may depend on symfony/http-kernel, dependency-injection, config, or Twig. A short spike could copy the array-shaping and view code into Blade components. Do not install the bundle in the Laravel app just to extract it; treat it as source reference.