- Is mmucklo/krumo-bundle a Laravel package?
- No. It is a Symfony 2/3 bundle that wires the Krumo dumper into the Symfony container, so it depends on AppKernel registration and bundle DI extension loading. Laravel consumes Symfony components but not Symfony bundles, so none of that lifecycle exists in a Laravel app. In Laravel, the bundle's entire value-add disappears and only the bare mmucklo/krumo library remains.
- Can I install mmucklo/krumo-bundle in a Laravel 10 or 11 application?
- Expect Composer resolution failures. The bundle targets Symfony 2.8 and 3.4, both long past end of life, and implicitly PHP 5.x through 7.x. On PHP 8.1+ with Laravel 10 or 11 the stale Symfony constraints will conflict, and even if forced through you should assume pre-PHP-7.2 syntax that fatals. Treat PHP 8 compatibility as unproven until a spike demonstrates otherwise.
- How do you install and configure mmucklo/krumo-bundle in Symfony?
- In its native Symfony 2/3 environment you install it with Composer, register MjmKrumoBundle in AppKernel, and adjust the display settings through the bundle configuration. You then use the provided Krumo service in controllers and services, or the Twig functions and filters inline in templates. None of these steps have a Laravel equivalent: there is no auto-discovery, no Facade, no service provider, and no config publish.
- What does Krumo actually do that var_dump and print_r do not?
- Krumo renders print_r and var_dump output as collapsible, color-coded HTML trees instead of raw text. It handles deeply nested arrays and objects with recursion guards, themed skins, and helpers for backtraces, includes, and loaded classes. For quick inspection of complex nested data in a browser it is genuinely easier to read than a plain dump.
- What should I use instead of Krumo for debugging a Laravel application?
- Use the dump() and dd() helpers, which ship via symfony/var-dumper and are already a framework dependency. Add barryvdh/laravel-debugbar for request, query, and view timing, Laravel Telescope for staged-environment observability, or Ray if the team prefers a desktop client. All of these are actively maintained and PHP 8+ compatible, which Krumo is not.
- Does mmucklo/krumo-bundle support PHP 8 and Laravel package auto-discovery?
- There is no evidence of PHP 8 support; the package predates it and targets EOL Symfony releases. Assume fatal errors or Composer constraint conflicts on a modern Laravel runtime until a spike proves otherwise. Auto-discovery is also out of the question, because auto-discovery applies to Laravel packages and this is a Symfony bundle.
- Is it safe to leave Krumo dumps enabled in production?
- No. Krumo renders full object graphs as HTML with inline CSS and JavaScript and limited escaping, which makes it an XSS vector. Dumps commonly contain request payloads, Doctrine entities, credentials, and PII, so accidental non-dev enablement is an information-disclosure incident. Gate any use behind app()->environment(['local', 'testing']) and never ship it enabled.
- Can I use Krumo in Laravel through a custom service provider?
- Technically yes, but discard the bundle and wrap the bare mmucklo/krumo library instead. Register a KrumoServiceProvider conditionally, add a dump_krumo() helper, and gate both on the local and testing environments. That is strictly more work than composer require --dev barryvdh/laravel-debugbar or simply calling dump(), so treat it as throwaway diagnostic scaffolding rather than application infrastructure.
- Is mmucklo/krumo-bundle actively maintained, and does it have test coverage?
- There is no evidence of active maintainership: roughly six GitHub stars, zero dependents, and targets for Symfony versions that reached end of life in 2018 and 2021. Assume any test coverage is absent. If you inherit it from a legacy Symfony service, document a removal date and a replacement before the migration starts.
- How do I migrate a Symfony app off Krumo without rewriting call sites?
- Do not migrate the bundle; migrate the behavior. Route all dumps through a single internal helper first, then swap that helper's implementation to symfony/var-dumper, Laravel Debugbar, or Telescope. Because call sites only touch the helper, the replacement costs zero churn across controllers and templates. Confirm the actual requirement first, since readable nested-array inspection is fully covered by dump() and dd().