Weave Code
Web Profiler Bundle Laravel Package
symfony/web-profiler-bundle
Provides the Symfony Web Profiler and debug toolbar for development. Inspect requests, routing, templates, database queries, logs, events, and performance metrics via an in-browser UI to speed up debugging and optimization.
Provides a development tool that gives detailed information about the execution of any request
Frequently asked questions about Web Profiler Bundle
- Can I use Symfony’s WebProfilerBundle directly in a Laravel project without Symfony components?
- No, the bundle is designed for Symfony and requires significant custom integration for Laravel. You’d need middleware to inject profiler data, custom collectors for Eloquent/Blade, and routing adjustments. Consider Laravel Debugbar or Blackfire instead for a drop-in solution.
- What Laravel-specific features are missing in Symfony’s WebProfilerBundle?
- The bundle lacks native support for Laravel’s Eloquent ORM, Blade templating, Queues, or Artisan commands. You’d need to build custom collectors or bridge Symfony’s Doctrine/Twig collectors via event listeners or query logging.
- How do I install WebProfilerBundle in a Laravel project using Symfony components?
- First, require `symfony/web-profiler-bundle` via Composer. Then configure it in `config/bundles.php` (Symfony-style) and create middleware to inject the profiler into Laravel’s request lifecycle. Use Symfony’s `Profiler` service in your controllers.
- Will this bundle work with Laravel’s Blade templating instead of Twig?
- No, the Twig collector is tightly coupled to Symfony’s templating. For Blade, you’d need to either disable template profiling or build a custom collector using Laravel’s `BladeEngine` events to log template rendering times and variables.
- Can I disable the toolbar in production while keeping profiling data for staging?
- Yes, use Symfony’s `PROFILER_ONLY_EXCEPTION` environment variable or Laravel’s `app.debug` config to toggle the toolbar. For staging, enable profiling via `.env` (e.g., `APP_DEBUG=true`) but restrict access to the `/_profiler` route with middleware.
- Does WebProfilerBundle support Laravel’s Eloquent ORM for query profiling?
- Not natively. You’d need to log Eloquent queries manually (e.g., via `Query::listen`) and feed them into a custom collector. Alternatively, use Laravel Debugbar’s Eloquent profiler or Blackfire for query analysis without integration overhead.
- How much performance overhead does this bundle add in development?
- Expect ~10–20% slower request times due to data collection. For Laravel, this could conflict with existing debug tools or caching layers. Test in staging first—disable in production entirely, as the toolbar exposes sensitive data.
- Are there alternatives to WebProfilerBundle for Laravel that offer similar features?
- Yes: **Laravel Debugbar** (lightweight, Eloquent/Blade support), **Blackfire** (professional profiling), **Tideways** (APM), or **Spatie’s Laravel Debugbar**. These are Laravel-native and require less customization than Symfony’s bundle.
- How do I extend the bundle to add custom collectors for my Laravel services?
- Create a service implementing Symfony’s `DataCollectorInterface`, bind it to Laravel’s container, and register it in the profiler’s `collectors` array. For example, log custom events or queue jobs via event listeners and expose them in your collector’s `collect()` method.
- What Laravel versions are compatible with Symfony’s WebProfilerBundle?
- The bundle itself has no Laravel-specific dependencies, but integration requires Laravel 8+ (for Symfony 5.4+ compatibility). For older Laravel versions, you’d need to manually bridge Symfony’s `HttpKernel` or use a polyfill like `symfony/http-foundation`. Test thoroughly—some features may break due to architectural differences.
Weaver
How can I help you explore Laravel packages today?