- What does debesha/doctrine-hydration-profiler-bundle do?
- It is a Symfony bundle that adds a profiler panel listing Doctrine hydrations performed while generating a response. The panel shows hydration timing and how many entities were hydrated, helping you spot ORM hydration bottlenecks. It is designed for development and test environments through Symfony's WebProfilerBundle.
- Is this package compatible with Laravel?
- Not natively. It is a Symfony bundle built around Symfony's profiler and DoctrineBundle, so Laravel integration is indirect. You would need a bridge such as symfony/web-profiler-bundle with laravel-debugbar, a custom Doctrine event listener, or a fork that replaces Symfony-specific dependencies.
- Can I use this bundle with Eloquent instead of Doctrine ORM?
- No. The bundle requires Doctrine ORM and profiles Doctrine hydration events, so Eloquent models are not covered. If your Laravel application uses Eloquent, this package is incompatible unless you adapt or fork it. Laravel-native tools such as Debugbar or Telescope are better fits for Eloquent query profiling.
- How do I install debesha/doctrine-hydration-profiler-bundle?
- Install it with Composer using composer require debesha/doctrine-hydration-profiler-bundle. Then register DebeshaDoctrineProfileExtraBundle in your Symfony application's bundle configuration, typically for dev and test environments only. The bundle must be registered after DoctrineBundle for the profiler integration to work correctly.
- Which Symfony, Doctrine ORM, and PHP versions are supported?
- The package advertises support for Symfony 5.4 through 7.x, Doctrine ORM 2.19+ or 3.0, and PHP 8.0+. Confirm these constraints against your application's composer.json before installing. For Laravel projects, the PHP and Doctrine ORM requirements still apply even though Laravel itself is not directly supported.
- Does this bundle work in production?
- It is primarily a development-focused profiling tool, not production-grade telemetry. The README recommends enabling it only in dev and test environments, where Symfony's profiler is available. For production monitoring, pair Doctrine profiling with APM tools such as Blackfire, New Relic, or custom logging.
- How does it integrate with Laravel's debugbar or Symfony profiler?
- In Symfony, it plugs into WebProfilerBundle and adds a dedicated hydration panel automatically once registered after DoctrineBundle. In Laravel, there is no direct integration, so you would need to bridge Symfony's profiler through packages like laravel-debugbar or write a custom Doctrine listener that records hydration metrics. A fork replacing Symfony dependencies with Laravel equivalents is possible but high effort.
- What hydration metrics does it show in the profiler?
- It lists all Doctrine hydrations performed during response generation. The profiler section shows how fast each hydration was and how many entities were hydrated. This helps identify expensive hydration strategies and entity graphs during development.
- Are there alternatives for profiling Doctrine hydration in Laravel?
- Yes. You can use Laravel Debugbar or Telescope for general query visibility, Blackfire or Xdebug for deeper performance tracing, or a custom Doctrine event listener for hydration-specific metrics. APM tools like New Relic or Tideways are better for production telemetry. This bundle is most useful when you already have a Symfony profiler stack.
- Is the bundle actively maintained and safe to use with Symfony 7 and Doctrine 3?
- The package metadata indicates Symfony 5.4-7.x and Doctrine ORM 2.19+/3.0 support, so it is intended to work with modern stacks. Before adopting it, check the latest release date, issue tracker, and changelog for breaking changes. Run it in staging with your actual entity mappings and hydration strategies to confirm compatibility.