Weave Code
Debug Bundle Laravel Package
symfony/debug-bundle
DebugBundle integrates Symfony VarDumper and MonologBridge's ServerLogCommand into the full-stack framework, giving developers powerful dump inspection and log viewing tools for debugging applications.
DebugBundle integrates the Symfony VarDumper component and MonologBridge's ServerLogCommand directly into the Symfony full-stack framework, giving developers powerful, first-class debugging tools with zero setup friction.
It bridges the gap between standalone components and the framework, exposing configuration, services, and console commands out of the box.
- Rich
dump()anddd()helpers powered by VarDumper - Web Debug Toolbar integration for dumps
server:logcommand to stream logs in real time- Seamless configuration via Symfony's bundle system
- Ideal for local development and debugging workflows
Enable it in bundles.php and start inspecting variables immediately.
Frequently asked questions about Debug Bundle
- Can I install symfony/debug-bundle in Laravel?
- No. symfony/debug-bundle is a full-stack Symfony bundle and depends on Symfony's kernel, DI extension, configuration tree, and profiler integration. Laravel does not use Symfony bundles, so installing it directly is unsupported and would require custom glue that is not recommended. For Laravel, use dump() and dd() from symfony/var-dumper plus Telescope or Debugbar instead.
- Does Laravel already include symfony/var-dumper for dump() and dd()?
- Yes. Laravel ships with symfony/var-dumper as a transitive dependency, so dump() and dd() are available out of the box. That covers the main VarDumper use case the DebugBundle provides in Symfony. You can also use a VarDumper dump server as a standalone development tool without installing the bundle.
- What is symfony/debug-bundle used for in Symfony?
- In Symfony full-stack apps, DebugBundle integrates the VarDumper component and MonologBridge's ServerLogCommand with the framework's configuration, profiler, and toolbar. It gives developers richer dump inspection and log-server tooling during development. It is not intended as a standalone library or a Laravel package.
- symfony/debug-bundle vs Laravel Telescope and Debugbar: which should I use?
- For Laravel applications, Telescope and Debugbar are the native options and cover request, query, log, and performance inspection. symfony/debug-bundle targets Symfony's profiler and toolbar, which Laravel does not use, so it adds little value there. Choose Telescope or Debugbar for Laravel and reserve DebugBundle for Symfony full-stack services.
- How do I use the VarDumper dump server with Laravel?
- Laravel already gives you dump() and dd() through symfony/var-dumper, and you can run a VarDumper dump server as a standalone development tool. You do not need symfony/debug-bundle to use the dump server in Laravel. DebugBundle mainly wires that tooling into Symfony's kernel and configuration.
- Can I use MonologBridge ServerLogCommand in Laravel?
- ServerLogCommand comes from MonologBridge and is wired into Symfony via DebugBundle's configuration. In Laravel, you can use Monolog directly and view logs with Laravel's log stack, Telescope, or a dedicated log viewer. Adopting the Symfony bundle just to get ServerLogCommand is not supported and adds unnecessary risk.
- Which Laravel and PHP versions are compatible with symfony/debug-bundle?
- symfony/debug-bundle follows Symfony's release cycle; Symfony 8 requires PHP 8.4 or newer, which may be ahead of your Laravel version's supported PHP range. Laravel pins its own Symfony component versions, so requiring the bundle can cause Composer conflicts. Check your Laravel and PHP constraints before considering any Symfony bundle, and prefer Laravel-native tooling.
- Is symfony/debug-bundle safe to enable in production?
- DebugBundle is development tooling and should not be enabled in production. In Laravel it is not supported at all, and enabling debug tooling in production risks leaking dump data and exposing internals. Keep dump() and dd(), Telescope, and Debugbar disabled or restricted outside local and staging environments.
- How do I migrate from symfony/debug-bundle to Laravel debugging tools?
- There is no real migration from symfony/debug-bundle to Laravel because the bundle was never a Laravel package. Instead, replace ad hoc var_dump or custom log files with Laravel's dump() and dd(), structured Monolog channels, and Telescope or Debugbar where appropriate. If you run both Laravel and Symfony, standardize on shared primitives like VarDumper and Monolog rather than forcing the bundle into Laravel.
- What are the best alternatives to symfony/debug-bundle for Laravel?
- For Laravel, the practical alternatives are built-in dump() and dd() from symfony/var-dumper, Laravel Telescope, Barryvdh Laravel Debugbar, and structured Monolog logging with a Laravel-native log viewer. symfony/debug-bundle itself is only appropriate for Symfony full-stack applications. Evaluate the specific gap you need to close before adding extra debugging dependencies.
Weaver
How can I help you explore Laravel packages today?