Weave Code
Ez Legacy Debug Bundle Laravel Package
mmz-srf/ez-legacy-debug-bundle
A Laravel debug bundle that brings legacy-style debugging helpers to older projects, offering simple dump-and-die utilities and debug output without requiring modern framework features. Useful for maintaining inherited or outdated applications.
mmz-srf/ez-legacy-debug-bundle brings legacy-style debugging helpers to modern Laravel applications. It offers a lightweight, configurable layer for inspecting variables, tracing execution, and surfacing diagnostic output without disrupting your existing workflow.
- Drop-in Laravel service provider and facade
- Legacy-compatible dump and print helpers
- Configurable output formatting and targets
- Environment-aware guards for production safety
- Simple integration with existing logging
Frequently asked questions about Ez Legacy Debug Bundle
- Is mmz-srf/ez-legacy-debug-bundle compatible with Laravel?
- No. mmz-srf/ez-legacy-debug-bundle is a Symfony bundle built for Symfony's WebProfilerBundle, not a Laravel package. It has no service provider, facades, config files, or Laravel container bindings, and it cannot be registered in a Laravel app. The Laravel label on some catalog entries is a mis-categorization.
- Can I install ez-legacy-debug-bundle with Composer in a Laravel project?
- You can try, but composer require will likely fail or force unacceptable Symfony 2 downgrades in a modern Laravel lockfile. Even if installed, Laravel will not boot the bundle because it relies on Symfony AppKernel bundle registration. There is no Laravel integration path, so do not add it to a Laravel project.
- Which Laravel versions does ez-legacy-debug-bundle support?
- None. The package supports no Laravel versions because it is a Symfony 2-era bundle. It was last released in 2015 and predates modern Laravel releases. For Laravel profiling, use Laravel Telescope or Laravel Debugbar instead.
- What does ez-legacy-debug-bundle actually do?
- It adds a custom Symfony data collector and Twig panel that surfaces eZ Publish Legacy debug information inside the Symfony WebProfiler. The panel shows legacy kernel state, template resolution, SQL queries, and similar diagnostics. It is a development-only convenience for Symfony 2 applications running eZ Publish Legacy.
- What PHP and Symfony versions does this bundle require?
- It assumes PHP around 5.5/5.6, Symfony 2.x, WebProfilerBundle, and the eZ Publish Legacy bridge. It is not compatible with modern PHP 7/8-era stacks or Symfony 5, 6, or 7. Those legacy versions are long past end of life.
- Do I need eZ Publish Legacy for this bundle to work?
- Yes. The bundle depends on eZ Publish Legacy and the ezsystems/ezpublish-legacy kernel to collect its debug data. Without a running eZ Legacy application, the collector has nothing to expose. If your team does not operate eZ Publish Legacy, there is no use case.
- Is ez-legacy-debug-bundle still maintained or archived?
- No, it is archived and unmaintained. The last release was 2015-09-16, with about 2 stars and 0 dependents, and there is no security response or PHP 8 compatibility work. Treat it as legacy technical debt, not an adoption candidate.
- Will it work on PHP 8 or Symfony 5, 6, or 7?
- No. Modern Symfony reworked the profiler collector and templating contracts this bundle relies on, and the Symfony 2 APIs it targets are gone. On PHP 8 you will hit compatibility errors with the old code and dependencies. Using it would require a fork and a rewritten collector.
- What are the best Laravel alternatives for profiler and debug output?
- For Laravel, use Laravel Telescope for request, query, and log inspection, or Laravel Debugbar for in-page dumps and timings. Symfony's VarDumper and Monolog cover general debugging needs. If you need eZ Legacy-specific data, you would write a custom watcher or collector rather than adopt this bundle.
- Is it safe to enable ez-legacy-debug-bundle in production?
- It is debug tooling and should never be enabled outside development. Because it hooks the request lifecycle and renders internal paths, SQL, and legacy kernel state, accidental production enablement could expose sensitive diagnostics. Add a hard dev-only environment guard if you ever fork it for internal use.
Weaver
How can I help you explore Laravel packages today?