Weave Code
Laravel Debugbar Laravel Package
fruitcake/laravel-debugbar
Integrate PHP DebugBar into Laravel to inspect requests in real time. Track queries, time, memory, routes, views, events, logs, and exceptions with an in-browser toolbar. Configurable collectors, storage, and easy setup for local development and debugging.
Debugbar for Laravel (Integrates PHP Debug Bar)
Frequently asked questions about Laravel Debugbar
- How do I install and enable fruitcake/laravel-debugbar in Laravel?
- Run `composer require fruitcake/laravel-debugbar`, then register the service provider in `config/app.php` under `providers`. Enable it via `debugbar.middleware` in `.env` (default: `APP_DEBUG=true`). No additional steps are needed for basic usage.
- Does fruitcake/laravel-debugbar work with Laravel 10+ and PHP 8.3?
- Yes, the package supports Laravel 10+ and PHP 8.3+. Version 4.2.x explicitly targets Laravel 13.x, but check the [GitHub releases](https://github.com/fruitcake/laravel-debugbar/releases) for compatibility notes if using older versions.
- Can I use this package in production? What are the risks?
- The package is **disabled by default in production** (when `APP_DEBUG=false`). Enabling it exposes sensitive data like query params or request payloads. Use `DEBUGBAR_FORCE_ALLOW_ENABLE` sparingly and restrict access via IP or environment flags.
- How do I track slow database queries with this debugbar?
- Enable query logging in `config/debugbar.php` by setting `query_explain_local_only` or `query_explain`. The toolbar will show execution times, explain plans, and duplicate queries. For CLI jobs, use `debugbar:query` Artisan command.
- Is there a way to customize or extend the debugbar collectors?
- Yes, you can add custom collectors by registering them via `Debugbar::collector(new CustomCollector())`. The package supports third-party extensions (e.g., Livewire, Inertia.js) and provides hooks for logging domain-specific metrics.
- Will this package slow down my Laravel application in debug mode?
- Minimal overhead is added (~5–10ms per request) due to query explain plans and data collection. Disable it in production or use `debugbar:storage` to log data without real-time rendering. Monitor performance with `debugbar:clear` commands.
- How do I hide sensitive data (e.g., auth tokens, passwords) from the debugbar?
- Use the `blacklist` option in `config/debugbar.php` to exclude collectors (e.g., `AuthCollector`). For dynamic filtering, implement a custom collector with `Debugbar::collector()` and override sensitive data handling.
- Can I integrate fruitcake/laravel-debugbar with Laravel Telescope or Clockwork?
- Yes, the package is designed to complement other debugging tools. Use it for real-time inspection while leveraging Telescope for persistent storage or Clockwork for API-focused debugging. Avoid redundancy by disabling overlapping collectors.
- Does this package support debugging CLI commands or scheduled jobs?
- Yes, use the `debugbar:clear` and `debugbar:query` Artisan commands to inspect CLI jobs. For scheduled tasks, ensure the debugbar middleware is enabled in your `app/Console/Kernel.php` or via environment flags.
- What alternatives exist if I need more advanced debugging features?
- For deeper observability, consider Laravel Telescope (persistent logs) or Clockwork (API-focused). For AI-assisted debugging, pair with Laravel Boost. If you need custom metrics, extend this package’s collectors or use a dedicated APM like Datadog.
Weaver
How can I help you explore Laravel packages today?