- Can I install havvg/dry-bundle in a Laravel app with Composer?
- No, not in any practical working sense. havvg/dry-bundle is a Symfony2 bundle, so it expects Symfony bundle registration, DI compiler passes, and Symfony services.yml/xml wiring rather than Laravel service providers and facades. Its symfony/symfony ~2.0 constraint and PSR-0 autoloading also conflict with modern Laravel dependency trees. Composer may resolve nothing useful, and there is no path where the bundle yields working Laravel functionality as-is.
- What does havvg/dry-bundle actually provide?
- It packages reusable DRY building blocks as a Symfony bundle and wires them into Symfony's dependency injection container. It also exposes a standard bundle configuration tree for tuning behavior and centralizes shared logic instead of duplicating it per project. The value is in the underlying patterns and helpers, not in the bundle as a Laravel dependency.
- Does havvg/dry-bundle support Laravel 10 or Laravel 11?
- No. The package is a Symfony2 bundle, not a Laravel package, and it has no Laravel service provider, facade, container tags, or Laravel-specific configuration. Modern Laravel requires PHP 8.1 or 8.2+ and a current dependency tree, while this bundle is Symfony2-era and PHP 5.3-era code. Treat it as reference material only, not a supported Laravel integration.
- Is havvg/dry-bundle maintained or safe for production?
- It is effectively unsupported, with Symfony2 and Symfony 2.8 LTS having reached end of life in November 2018 and no security patches since. Adoption is very low, with roughly 9 stars and 0 dependents, so there is no downstream battle-testing or community support surface. It should not enter production dependencies; any useful patterns should be reimplemented and tested in your own codebase.
- How does havvg/dry-bundle register services in Laravel's container?
- It does not. The bundle registers and autoconfigures services through Symfony's DI container, bundle extension, and services.yml/xml configuration, none of which is portable to Laravel. Laravel uses service providers, facades, container bindings, and tags, so integration would require a conceptual rewrite. There is no transferable wiring layer between the two frameworks.
- Can I reuse havvg/dry-bundle helpers in a Laravel project?
- Only by extracting and rewriting the patterns, never by adding the bundle as a dependency. Audit the bundle class, DI extension, Resources/config XML, and any Model or Util classes, then triage each helper against current needs. Accepted patterns should become Laravel-idiomatic traits, base classes, Eloquent scopes, service providers, or container tags with tests. Keep any vendored utility code deletable and attributed.
- What alternatives should I use instead of havvg/dry-bundle in Laravel?
- Use Laravel-native tools such as traits, Illuminate\Support\Str and Arr, Eloquent scopes, service providers, and container tags. Maintained Laravel packages that solve the specific duplication problem are safer than an abandoned Symfony2 bundle. If you are actually on Symfony, use current maintained Symfony equivalents rather than Symfony2-era code.
- What PHP versions does havvg/dry-bundle require, and does it work with PHP 8?
- It is PHP 5.3-era code tied to a symfony/symfony ~2.0 constraint, so it is not compatible with modern PHP 8.x applications. PHP 8's stricter types, dynamic property deprecations, and removed functions create conflicts with this codebase. Modern Laravel versions require PHP 8.1 or 8.2+, so the bundle cannot fit a current Laravel stack.
- How should I test a Laravel reimplementation of havvg/dry-bundle patterns?
- Write Laravel-idiomatic tests for each extracted trait, scope, or service provider method rather than testing the original bundle. Cover container bindings and tags, edge cases in string or array helpers, and Eloquent model behavior where relevant. Keep the implementation small and deletable so tests document the pattern without creating a new maintenance burden. Use your normal PHPUnit or Pest setup and avoid pulling in Symfony2 test scaffolding.
- What should I audit in havvg/dry-bundle before deciding to reuse anything?
- Start with src/Havvg/Bundle/DRYBundle: the bundle class, DI extension, Resources/config XML, and any Model or Util classes. Enumerate the concrete helpers and score each against relevance, overlap with existing Laravel features, and long-term maintenance cost. Stop early if nothing clears the bar and record a no-adopt decision. If a pattern is accepted, document it as an ADR and reimplement it with tests instead of depending on the bundle.