Weave Code
Yii Debug Laravel Package
yiisoft/yii-debug
Yii Debug is a debugging extension for Yii applications that provides a toolbar and panels for logs, database queries, performance profiling, request data, and more, helping developers inspect and troubleshoot application behavior during development.
Yii debug panel extension
Frequently asked questions about Yii Debug
- Can I install yiisoft/yii-debug in a Laravel application?
- No, not in any practical sense. It is a Yii extension that binds into the Yii DI container, middleware stack, event dispatcher and view layer, none of which exist in Laravel. Wiring it into Laravel would mean reimplementing the container bindings, middleware registration and panel rendering yourself, at which point you have written your own package and inherited only the maintenance burden.
- Is Yii Debug the same thing as Laravel Telescope or Laravel Debugbar?
- They solve the same problem but share no code and no architecture. Yii Debug provides a toolbar and panels for logs, database queries, profiling, request data and similar collectors inside a Yii application. Laravel's equivalents are Telescope, Debugbar and Clockwork, which hook into Laravel's service container and HTTP kernel. There is only thin overlap at the PSR-7/PSR-15 boundary.
- What panels and features does yii-debug provide?
- It ships a debug toolbar plus panels covering logs, database queries, performance profiling and request data, aimed at inspecting application behaviour during development. Collectors capture request, log, SQL and profiling information and the panel UI renders it. For a full list you should read the source collectors directly, since the README excerpt and repository metadata are not available.
- Which Yii version does this package target, Yii 2 or Yii 3?
- The yiisoft/* namespace strongly indicates the Yii 3 line, which is PSR-7 and PSR-15 middleware based and therefore more portable than Yii 2. That is an inference from the package name, not a confirmed fact, and the repository field is listed as unknown. Confirm the supported Yii major line and the PHP 8.x floor with the maintainer before depending on it.
- How do I install Yii Debug in a Yii 3 service?
- Add it as a require-dev dependency in the Yii service that needs it, then register the debug middleware and panel route in the development configuration only. Because it is a Yii extension, installation is straightforward inside a Yii application and requires no custom glue code. Verify the environment guard fires before you rely on it.
- Is it safe to run Yii Debug in staging or production?
- Debug panels expose environment variables, configuration, SQL, request bodies, headers and session data, so they are only safe as dev-only tooling gated behind an environment check. Any path where the panel is reachable in staging or production is a data-exposure incident, not a minor misconfiguration. Check whether the package enforces an environment guard itself or leaves that entirely to your config, and confirm the authorization story for the panel endpoint.
- Where does Yii Debug store its collected debug data?
- The storage backend is not documented in the available metadata, so treat it as unknown until you read the source. Plausible options are files, SQLite or in-memory, and each has different implications for disk usage and for how long sensitive request data lingers. Ask the maintainer where data is persisted and what the retention and rotation defaults are.
- How does yii-debug compare to Telescope, Debugbar and Clockwork for a Laravel team?
- For a Laravel stack the comparison is not close: Telescope, Debugbar and Clockwork are native, widely used and actively maintained against current Laravel and PHP releases. Yii Debug has effectively zero direct fit with Laravel and cannot be co-installed in the same composer graph as a Laravel app. Its only value to a Laravel team is as design input, such as comparing collectors offered, storage model and UI affordances.
- What are the maintenance and bus-factor risks with this package?
- Community scrutiny is very low, with roughly 33 stars and a repository field reported as unknown. That points to a near-single-maintainer project with no visible release cadence, meaning you would own your own patches. That is acceptable for a dev convenience but not acceptable for anything with a production surface.
- What should I check before trusting the distributed artifact?
- Verify the canonical source repository and confirm it matches the artifact you install, including tag signing and CI provenance. Check whether the package is tracked against current PHP 8.x releases and what its transitive psr/* and yiisoft/* constraints pin, since those can conflict with an existing lockfile. Provenance verification is a hard gate for a tool that ships a debug panel, not a formality.
Weaver
How can I help you explore Laravel packages today?