- Is kutny/tracy-bundle compatible with Laravel?
- No. It is a Symfony bundle that wires the Tracy debugger into Symfony's dependency injection container and event system through a Bundle class, compiler passes, and Symfony configuration nodes. Laravel has no Bundle contract, so there is nothing to register in config/app.php and the bundle layer will not function. The only portable piece is the upstream tracy/tracy library, which is framework-agnostic PHP and can be bootstrapped manually.
- How do I install the Tracy debugger in a Laravel application?
- Do not install kutny/tracy-bundle. If you specifically need Tracy, require the upstream tracy/tracy package at a pinned version and write a thin Laravel service provider that registers Tracy's Debugger only when the app environment is local. Gate Debugger::$showBar and Debugger::$productionMode behind explicit config, set Debugger::$email to null, and point Tracy's log directory at storage/logs/tracy with .gitignore coverage.
- What is the difference between Tracy and Laravel Ignition?
- Both provide friendly error screens, stack traces, and debugging helpers, but Ignition is built for Laravel and ships as part of the default dev stack through spatie/laravel-ignition. Tracy adds its blue-screen error pages, dump() and bardump() helpers, a debug bar, and an error mailer. For a Laravel codebase the feature overlap is near-total, so Tracy adds dependency and maintenance risk without a clear capability gain.
- Does kutny/tracy-bundle support PHP 8 and modern Laravel versions?
- The bundle targets PHP 7.1 and 7.2 with Symfony 3.4/4.0-era conventions and Tracy 2.4/2.5-era APIs. It has been archived since 2018 and PHP 8.x compatibility is unverified and likely broken in the bundle layer. You should expect friction around error handling and set_error_handler signatures if you try to run it on modern PHP.
- Is kutny/tracy-bundle still maintained?
- No. The repository has been archived since 2018-01-30, with no releases in roughly seven years and no security response path. It has zero dependents and only 28 stars, so there is little downstream signal that anyone runs it in production. Any vulnerability in the Tracy 2.x-era code is inherited with no patch lane.
- What are the best Laravel alternatives to Tracy's debug bar and dump tools?
- Laravel already ships equivalent or better tooling: spatie/laravel-ignition for error pages, symfony/var-dumper plus barryvdh/laravel-debugbar for dumps and panels, Laravel Telescope for request and query inspection, and Clockwork for profiling. These are actively maintained and designed for Laravel's container and lifecycle. Choosing them avoids the unmaintained Tracy dependency entirely.
- Can I use Tracy's dump() function in Laravel instead of dd()?
- Technically yes, but only by depending on tracy/tracy directly and bootstrapping it yourself; this Symfony bundle will not do it for you. Laravel's native dd() and dump() helpers, backed by symfony/var-dumper, plus Debugbar already cover that workflow. Adding Tracy for this narrow use case means inheriting an unmaintained API surface for little benefit.
- Is it safe to enable the Tracy debugger in production?
- No. Tracy's error handler renders and often persists stack traces and environment details, so misconfigured outside local it becomes an information-disclosure vector. Tracy's mailer has historically sent debug dumps by email, which is a data-exfiltration risk in regulated environments. If you use Tracy at all, hard-gate it to the local environment and disable the mailer by setting Debugger::$email to null.
- How do I configure Tracy manually without the Symfony bundle?
- Require a pinned, audited version of tracy/tracy and create a Laravel service provider that registers Tracy's Debugger only when app()->environment('local') is true. Explicitly control Debugger::$showBar and Debugger::$productionMode from config, disable the mailer with Debugger::$email = null, and direct logs to storage/logs/tracy. Budget one to two engineer-days for the provider and hardening, and verify behavior against your target PHP and Laravel versions.
- What Symfony and Tracy versions does kutny/tracy-bundle target?
- It is built for Symfony 3.4/4.0-era bundle conventions and Tracy 2.4/2.5-era APIs, targeting PHP 7.1 and 7.2. That makes it a reasonable cheap debug-bar drop-in only for a legacy Symfony application already on that stack and in maintenance mode. It is not a fit for a Laravel application, where the correct integration is not to integrate this artifact at all.