- What is skobkin/useful-bundle?
- It is a Symfony 2 bundle that collects reusable helpers such as custom form types (date-range and dependent-select widgets), Doctrine DQL functions, and Twig extensions. It is not a Laravel package and does not target Laravel applications. Treat it as a legacy Symfony artifact rather than a Composer dependency for a Laravel project.
- Is skobkin/useful-bundle compatible with Laravel?
- No. There is no Laravel integration surface: no service provider, no facade, no publishable config, no package discovery manifest, and no Laravel version constraint. The bundle plugs into Symfony 2's kernel and bundle lifecycle, which does not exist in Laravel. There is no seam to integrate at, only code to read.
- Can I install skobkin/useful-bundle with Composer in a Laravel app?
- Effectively no. The bundle's symfony/* constraints target Form 2.x, Twig 1.x, and HttpKernel-era components, while modern Laravel pulls Symfony 6/7 transitive packages. Expect a Composer resolver deadlock rather than a clean install. The constraint set is the proof, so do not spend engineering time trying to force it.
- Which Symfony and PHP versions does skobkin/useful-bundle support?
- It targets Symfony 2 with Twig 1 and the Symfony 2 Form component, and Symfony 2 reached end of life in November 2018. There is no declared PHP 8.x compatibility and no expectation of fixes. The idioms it uses, such as Twig_Extension and the Symfony 2 Form setDefaultOptions/getName lifecycle, are removed or hard-deprecated in Symfony 5+/Twig 3.
- Is skobkin/useful-bundle maintained?
- No. It has zero stars, zero dependents, and effectively no community validation or issue traffic. There is no downstream project exercising the code and no maintainer activity to rely on. You would become the sole QA function for code you did not write.
- Is skobkin/useful-bundle safe to use in production?
- Not recommended. It is unmaintained and unpatchable: no PHP 8.x compatibility fixes, no security advisories, and no CVE response, so any vulnerability inherited from its Symfony 2/Twig 1 era becomes yours. The DQL slice is especially risky because a subtly incorrect FunctionNode can emit wrong SQL that passes review and corrupts reporting. Licensing and fork provenance are also unresolved and should be treated as a release blocker before any code is copied.
- What features does skobkin/useful-bundle include?
- The feature inventory is a grab-bag rather than a single capability: custom form types (date-range and dependent-select widgets), Doctrine DQL functions, and Twig extensions. In a Laravel codebase those land on three different owners: UI components, query layer, and view layer. Evaluating it as one package is a category error even before compatibility is considered.
- Can I reuse the Doctrine DQL functions from skobkin/useful-bundle in Laravel?
- Only if the target application deliberately runs Doctrine ORM instead of Eloquent, which is atypical and should be confirmed first. Even then, reuse means vendoring individual classes and rewriting their base classes and interfaces after stripping Symfony plumbing. A subtly incorrect DQL function can silently emit wrong SQL, so this slice carries disproportionate risk relative to its small line count.
- What are the alternatives to skobkin/useful-bundle for Laravel projects?
- For Laravel, reimplement the small helpers you actually need; a date-range field or dependent-select widget is often about 40 lines with Blade or Livewire components. For DQL functions, use a maintained Doctrine package only if you are deliberately on Doctrine ORM. Do not adopt this bundle as a dependency; at best it is a reference implementation.
- How should I evaluate or test skobkin/useful-bundle before reusing code?
- First name the exact capability that triggered the evaluation: a date-range field, a dependent-select widget, a DQL function, or a Twig helper. Do not spend time proving Composer installation; the dependency constraints already show it will not resolve in a modern Laravel app. If you reuse any code, audit every file for PHP 8, Symfony 5+, and Twig 3 API removals and confirm the fork's license terms and attribution obligations before copying.