- Can I use ais/haribundle in Laravel 8/9/10?
- No, this bundle is explicitly tied to Symfony 2.7.4 and relies on Symfony-specific components like AppKernel, FOSRestBundle, and NelmioApiDocBundle, which have no Laravel equivalents. Laravel uses ServiceProviders, API Resources, and Spatie/L5-Swagger for API documentation instead.
- What is 'Hari' in ais/haribundle, and how does it work?
- The package description is vague—'Hari' isn’t defined in the README or documentation. Without clarity, you can’t assess its purpose, functionality, or relevance to Laravel. It may be a custom library, service, or business logic, but there’s no evidence it aligns with Laravel’s ecosystem.
- Why does ais/haribundle require Symfony 2.7.4, and can I bypass it?
- The bundle hardcodes dependencies on Symfony 2.7.4 (EOL since 2017), including deprecated components like SwiftMailer and Monolog. Even if you install it, Laravel’s architecture (e.g., Eloquent, ServiceProviders) conflicts with Symfony’s bundle system. Bypassing it would require a full rewrite, which isn’t feasible without forking and maintaining the codebase.
- Are there Laravel alternatives to FOSRestBundle or NelmioApiDocBundle?
- Yes. Replace FOSRestBundle with Laravel’s built-in API Resources or Spatie’s [Laravel API](https://spatie.be/docs/laravel-api). For API documentation, use Spatie’s [Laravel API Docs](https://spatie.be/docs/laravel-api-docs) or DarkaOnline’s [L5-Swagger](https://github.com/DarkaOnLine/L5-Swagger). These are actively maintained and compatible with modern Laravel.
- Will ais/haribundle work with Doctrine ORM in Laravel?
- No. The bundle uses Doctrine ORM 2.4.8 (released in 2014), which conflicts with Laravel’s Eloquent or modern Doctrine 2.10+ integrations. Laravel’s Doctrine packages (like [laravel-doctrine](https://github.com/laravel-doctrine)) require updated versions. Migrating this bundle’s ORM logic would need a complete rewrite.
- Is ais/haribundle secure for production use?
- No. Symfony 2.7.4 has unpatched vulnerabilities (e.g., CVE-2017-12617 in SwiftMailer), and the bundle includes deprecated dependencies like `ircmaxell/password-compat`. Laravel’s built-in security (e.g., password hashing) and modern PHP versions (8.0+) provide better protection. This bundle introduces unnecessary risk.
- How do I test ais/haribundle in a Laravel project?
- You can’t. The bundle relies on Symfony’s `liip/functional-test-bundle`, which has no Laravel equivalent. Laravel uses Pest or PHPUnit with Laravel extensions (e.g., `laravel/pint`, `nunomaduro/collision`). Without a Laravel-compatible test layer, integration testing is impossible.
- What’s the maintenance status of ais/haribundle?
- The package is abandoned—no updates, issues resolved, or community activity since its creation. The README even asks users to email the author (`vizzlearn@gmail.com`) for fixes. Integrating it would require indefinite maintenance of a deprecated stack, which is unsustainable.
- Can I migrate ais/haribundle’s features to Laravel?
- Only if you rewrite it from scratch. Key steps would include: converting Symfony bundles to Laravel ServiceProviders, replacing FOSRestBundle with API Resources, updating Doctrine ORM to a Laravel-compatible version, and reimplementing API docs with Spatie/L5-Swagger. The effort may exceed the value of the original bundle’s vague 'Hari' functionality.
- Are there any success stories or case studies for ais/haribundle?
- No. The package has minimal GitHub activity (few stars, no forks), no public case studies, and no Laravel-specific documentation. The lack of adoption suggests it either solves a niche problem (unclear what) or is abandoned. Proceed with caution—modern Laravel packages offer better support and features.