- Can I use szczyglis/extended-dump-bundle in a Laravel application?
- No. It is a Symfony bundle built for Symfony 4.4, 5.x and 6.x, so it does not register with Laravel's service container or service providers. Laravel developers should use native tools such as dump(), dd(), Telescope or a maintained VarDumper integration instead. Only Symfony applications should consider adding it as a require-dev dependency.
- What does szczyglis/extended-dump-bundle actually add to Symfony's dump() function?
- It extends the framework's dump output and attaches a dockable debug window to the application that collects debug information from all dumps. The goal is richer, more readable output for arrays, objects and deeply nested data. It complements the standard dump() function rather than replacing your existing debugging workflow.
- How do I install szczyglis/extended-dump-bundle with Composer?
- Install it as a development dependency with composer require --dev szczyglis/extended-dump-bundle. Because it is a Symfony bundle, you then register it in config/bundles.php or let Symfony Flex handle registration. Pin an exact version so upgrades stay deliberate, and keep the package out of production installs.
- Which Symfony and PHP versions does extended-dump-bundle support?
- The package states support for Symfony 4.4, 5.x and 6.x, which fits legacy and maintained Symfony 6 applications. Symfony 7 support is not confirmed, and the tested PHP versions are not clearly documented in the package description. Validate it against your exact Symfony and PHP combination in a disposable sandbox before adopting.
- How do I make sure extended-dump-bundle is disabled in production?
- Register the bundle only in your dev and test environments, for example by gating config/bundles.php on the APP_ENV value or using when@dev blocks in Symfony configuration. Keep it in require-dev so production builds never install it. Run a production-like CI job with the bundle absent to prove nothing depends on it.
- Does extended-dump-bundle conflict with symfony/var-dumper or the Symfony debug toolbar?
- It is designed to work alongside Symfony's VarDumper, so in principle it should not replace it. In practice the bundle adds its own dockable window that may overlap with the debug toolbar and existing dump-server workflows. Test both together on a feature branch and compare the output before relying on it.
- Does extended-dump-bundle capture sensitive request, session or environment data?
- The package description does not clearly document what data the debug window collects beyond dump output. Because dumps frequently include request payloads, session contents and environment values, treat it as a potential data exposure path. Keep it strictly dev-only and avoid dumping secrets while it is enabled.
- Is szczyglis/extended-dump-bundle actively maintained?
- Adoption is very low, with around 3 stars, no dependents and a last release in August 2024. That means limited community testing, few reported issues and no guaranteed maintainer response path. If you adopt it, assign internal ownership and budget for forking or removing it later.
- What are the alternatives to extended-dump-bundle for debugging Symfony or Laravel apps?
- Symfony developers can rely on native VarDumper, the Symfony profiler and the debug toolbar, all of which are actively maintained. Laravel teams have dump(), dd(), Telescope and Ray-style tooling that cover the same inspection needs. Compare the bundle's output against these maintained options before adding another dependency.
- How should I evaluate extended-dump-bundle before using it in a real project?
- Pilot it in a single non-critical Symfony 6 service on a feature branch with an exact pinned version. Compare its output and behaviour against native dump() and the profiler, and confirm your CI still passes with the bundle disabled. Document the rollback path of removing the dependency and restoring native dump configuration.