Weave Code
Debug Bundle Laravel Package
symfony/debug-bundle
Symfony DebugBundle integrates the VarDumper component and MonologBridge’s ServerLogCommand into the full-stack framework, enhancing debugging and server-side logging during development with tight Symfony tooling support.
Provides a tight integration of the Symfony VarDumper component and the ServerLogCommand from MonologBridge into the Symfony full-stack framework
Frequently asked questions about Debug Bundle
- Can I use Symfony DebugBundle in a vanilla Laravel app without Symfony components?
- Yes, but selectively. You can integrate just the VarDumper component for enhanced `dump()` functionality by requiring `symfony/var-dumper` directly, bypassing the full bundle. The MonologBridge features require PSR-3 logging (Laravel’s Monolog package satisfies this). Avoid the full bundle if you don’t need Symfony’s web profiler or ServerLogCommand.
- How do I install Symfony DebugBundle in Laravel without conflicts?
- Run `composer require symfony/debug-bundle --with-all-dependencies` and check for conflicts with `composer why-not symfony/debug-bundle`. If conflicts arise (e.g., with `laravel/debugbar` or `telescope`), disable one toolbar or use composer overrides. Ensure your `symfony/*` packages are version-locked to avoid breaking changes.
- Will Symfony DebugBundle replace Laravel Debugbar or Telescope?
- Partially. DebugBundle’s VarDumper replaces Laravel’s basic `dump()`, but its web profiler toolbar may conflict with Debugbar. Telescope offers more advanced features (e.g., query logging, job monitoring). Use DebugBundle only if you need Symfony-specific tools like request/response inspection or MonologBridge’s ServerLogCommand.
- What Laravel versions support Symfony DebugBundle?
- Laravel 10+ works if Symfony components (e.g., `symfony/http-foundation:^6.4`) are compatible. For Laravel 9 or older, conflicts may arise due to Symfony 6.x+ features (e.g., PSR-15 middleware). Test in a staging environment first, as some Symfony Profiler features may not render in Laravel’s Blade views.
- How do I enable/disable DebugBundle in production?
- Disable it entirely in production by setting `APP_DEBUG=false` in your `.env`. DebugBundle adds ~5–15% overhead, so gate it behind middleware or feature flags. Avoid exposing the web profiler toolbar in production, as it may leak sensitive data (e.g., request headers, stack traces).
- Does Symfony DebugBundle work with Laravel’s Monolog setup?
- Yes, but configure it carefully. DebugBundle’s MonologBridge enhances logging with structured context (e.g., request IDs). If you’re using `monolog/monolog`, ensure your `monolog.config` includes the `ServerLogCommand` and that Laravel’s Monolog handlers are compatible with Symfony’s processors. No extra setup is needed if you’re already using PSR-3 logging.
- Can I use Symfony DebugBundle’s VarDumper without the full bundle?
- Absolutely. Require only `symfony/var-dumper` via Composer to replace Laravel’s `dump()` with Symfony’s enhanced VarDumper, which handles circular references and complex objects better. This avoids pulling in the entire DebugBundle and its dependencies. Example: `composer require symfony/var-dumper`.
- How does Symfony DebugBundle handle exceptions compared to Laravel’s default?
- DebugBundle integrates with Symfony’s exception handling to show detailed stack traces, request/response data, and middleware context—similar to Laravel’s default but with Symfony’s VarDumper formatting. For hybrid apps, this can provide deeper insights than Laravel’s `dd()` or `dump()`. If using custom exception handlers, ensure they’re compatible with Symfony’s error controller.
- Are there performance concerns with DebugBundle in high-traffic Laravel apps?
- Yes. DebugBundle adds ~10–20ms per request when enabled, which can impact high-traffic apps. Disable it in production (`APP_DEBUG=false`) and consider opt-in routes via middleware. For performance-critical paths, avoid the web profiler toolbar entirely. Benchmark your app with and without the bundle to assess the impact.
- What alternatives exist for Laravel if I don’t want to use Symfony DebugBundle?
- For debugging, use Laravel’s built-in `dd()`, `dump()`, or packages like `barryvdh/laravel-debugbar` (Debugbar) for a toolbar. For advanced debugging, `laravel/telescope` offers query/log/job inspection. For Monolog enhancements, stick with `monolog/monolog` or `spatie/laravel-logging`. If you need Symfony-specific tools, consider `symfony/var-dumper` alone or migrate to a full Symfony stack.
Weaver
How can I help you explore Laravel packages today?