- Is shtumi/useful-bundle a Laravel package?
- No. It is a Symfony 2 bundle shipped in the legacy ShtumiUsefulBundle convention, with DependencyInjection, Form/Type, Doctrine, and Twig directories. It has no Laravel ServiceProvider, facade, container bindings, or illuminate dependencies, so it will not integrate with a Laravel application.
- Can I install shtumi/useful-bundle in a Laravel 10 or 11 app?
- You should not, and Composer will almost certainly refuse. The bundle pins symfony packages to ~2.x constraints while Laravel 10 and 11 require Symfony 6 or 7 components, so dependency resolution fails at install time. This is a fast, cheap failure, but it means there is no viable direct integration path.
- What does shtumi/useful-bundle actually provide?
- It is a grab-bag of Symfony utilities: Twig filters and functions such as pluralize and HTML-safe truncate or wordwrap, custom Doctrine DQL functions, reusable Symfony form types like datepicker, daterange, autocomplete, and dependent filtered entity selects, plus validator constraints. These are all Symfony and Doctrine primitives rather than Laravel building blocks. Only the plain text helpers are easily portable.
- What Laravel version is supported by shtumi/useful-bundle?
- None. The package targets Symfony 2.x and code from the PHP 5.x to 7.x era, and Symfony 2.8 extended support ended in November 2019. There is no declared Laravel support, no Laravel test matrix, and no upgrade path to modern Symfony or Laravel versions.
- Does shtumi/useful-bundle work with Doctrine ORM in Laravel?
- Not as an installed bundle. Even if you use laravel-doctrine/orm, the package relies on Symfony bundle bootstrapping, dependency injection, and configuration, none of which Laravel provides. You could copy specific DQL function classes into a Doctrine setup, but that is a manual port rather than package integration.
- Why does composer require shtumi/useful-bundle fail in a Laravel app?
- The failure is dependency resolution, not runtime. The bundle's symfony ~2.x constraints conflict with the Symfony 6 or 7 components that Laravel 10 and 11 pull in transitively. Composer stops before installation, which is the best outcome because the code would not wire into Laravel anyway.
- Is shtumi/useful-bundle maintained and safe for production?
- Treat it as unmaintained and high risk. Symfony 2.8 is long past end of life, so there are no security patches, no PHP 8 compatibility guarantee, and roughly 110 stars with zero Packagist dependents, meaning no production adopter has validated it. The bus factor is effectively one maintainer, with no release cadence to measure.
- Are there Laravel alternatives to its Symfony form types?
- Yes, but not as a single package. In Laravel you would build datepicker, daterange, autocomplete, and dependent select behavior with Blade components, FormRequest validation rules, a JavaScript datepicker such as Flatpickr or Tempus Dominus, and Livewire for dependent selects. Laravel deliberately separates form rendering, validation, and data transformation, so a direct port would inflate scope.
- How do I port its Twig extensions to Laravel Blade?
- Only the text helpers are worth porting. Reimplement pluralize, HTML-safe truncate, and wordwrap as Blade directives or namespaced helper classes registered through composer.json files, using Laravel's Str helpers where they already fit. Keep behavior covered by tests so the port matches the original output.
- What license does shtumi/useful-bundle use, and can I fork it?
- Check the repository's composer.json and LICENSE file before copying anything, because attribution obligations govern any port. Many older Symfony bundles are MIT licensed, but confirm rather than assume. If you fork, keep the license and attribution intact and plan to own maintenance, since the upstream has no release cadence.