- Can I use nicodemuz/doctrine-fixtures-timing-bundle in a Laravel application?
- Not directly. It is a Symfony bundle that must be registered in bundles.php and it instruments doctrine/doctrine-fixtures-bundle, neither of which exists in Laravel's default stack. Laravel's data-loading story is Eloquent factories, seeders, and db:seed. Treat any expectation of dropping it into a Laravel app as incorrect.
- Does this package support Laravel 10 or Laravel 11?
- No. The package is a Symfony bundle and declares no Laravel support, since Laravel has no bundle registration mechanism or kernel.event_listener tags out of the box. Its compatibility surface is Symfony and doctrine/doctrine-fixtures-bundle versions, not Laravel versions. Check composer.json for the exact constraints before assuming any framework compatibility.
- How do I install and register doctrine-fixtures-timing-bundle in a Symfony project?
- Install it with Composer as a dev dependency, then enable it in config/bundles.php and add any bundle configuration under its config key. Because the v1.0.0 release notes contain only an auto-generated changelog link, confirm exact registration and configuration details against the README and the package source. The bundle is intended only for development and testing environments.
- What does this bundle actually measure — Symfony profiler data or raw fixture execution time?
- The stated purpose is timing instrumentation around fixture execution so you can see per-fixture and total load times. Whether it hooks the Symfony profiler or simply wraps execution in microtime calls is not documented in the available material. That distinction matters, because standalone microtime timing is portable to Laravel while a profiler tie-in is not. Read the listener source to confirm before planning any adaptation.
- How do I get per-fixture load times from Laravel seeders instead?
- Reimplement the pattern rather than installing the bundle. A small internal listener bound to Laravel's Seeder and console Command events can capture microtime around each seeder run and print per-seeder and total durations. That is roughly 50 to 100 lines of code and keeps you on native Laravel tooling. Use this package as a reference implementation for the output format and timing hooks.
- Should doctrine-fixtures-timing-bundle be a production dependency?
- No. It is a developer-observability tool for fixture execution, so it belongs in a require-dev position at most. Nothing about it is runtime infrastructure, and fixture loading itself should not run in production. Install it only in Symfony or Symfony-plus-Doctrine environments used for development and CI.
- Which version of doctrine/doctrine-fixtures-bundle does this bundle require?
- The available material does not state a version constraint, and the v1.0.0 release notes contain no compatibility matrix. This matters because the doctrine-fixtures-bundle v2 rewrite changed fixture-loading internals, which can break event listeners. Read composer.json and the listener code to see which internals it actually depends on before committing to it.
- How much effort is it to adapt this package for a Laravel codebase?
- Expect a custom adapter rather than a drop-in install. You would write a Laravel service provider that registers an equivalent Artisan event listener and reimplement whatever timing and formatting logic the bundle performs. In practice, extracting the pattern and rewriting it as a seeder timing listener is the higher-value path. Budget a short spike to read the instrumentation code first.
- Is nicodemuz/doctrine-fixtures-timing-bundle actively maintained?
- There is no clear signal. The v1.0.0 release notes contain only an auto-generated Full Changelog link, with no migration notes or compatibility matrix, and no prior version history is available to diff against. The 1.0.0 tag suggests the author intends the public API to be stable. Check issue and pull request activity, CI status, and test coverage before depending on it.
- What are the alternatives for spotting slow seed data in Laravel?
- Measure seeder and factory execution directly with microtime in a custom listener or a db:seed command decorator, which gives you the same per-seeder and total timings this bundle provides for Doctrine fixtures. Laravel Telescope and query logging can help identify the underlying slow queries. For Doctrine-based Laravel apps, you can also profile the ORM directly rather than relying on a Symfony bundle.