Weave Code
Code Weaver
Helps Laravel developers discover, compare, and choose open-source packages. See popularity, security, maintainers, and scores at a glance to make better decisions.
Feedback
Share your thoughts, report bugs, or suggest improvements.
Subject
Message

Yii2 Debug Laravel Package

yiisoft/yii2-debug

Yii2 Debug adds a bottom-page debug toolbar and detailed standalone panels for Yii 2 apps, helping you inspect requests, logs, profiling, DB queries, and more during development. Install via Composer and enable the debug module in config.

View on GitHub
Deep Wiki
Context7

yiisoft/yii2-debug adds a powerful debug toolbar and dedicated debug pages to Yii 2 apps, making it easy to inspect requests, application state, and performance during development. Once enabled via app config, it injects a toolbar into every page and exposes richer details through standalone panels.

Key features:

  • Toolbar on every page with quick access to profiling data
  • Standalone debug views for deeper inspection
  • Request/response, routing, and config visibility
  • Performance & profiling insights to spot bottlenecks
  • IP-based access control for safer local debugging
Frequently asked questions about Yii2 Debug
Can I use yiisoft/yii2-debug in Laravel for debugging SQL queries or exceptions?
No, this package is designed exclusively for Yii 2.x and won’t work in Laravel. Laravel alternatives like `barryvdh/laravel-debugbar` or `tightenco/ziggy` provide similar SQL logging and exception tracking while integrating seamlessly with Laravel’s middleware and service providers.
Will yiisoft/yii2-debug work with Laravel’s Eloquent ORM or Blade templates?
Absolutely not. This package relies on Yii’s CDbCommand and component model, which are incompatible with Laravel’s Eloquent ORM and Blade templating system. Laravel-native tools are required for proper integration with its architecture.
How do I migrate from Yii’s debug toolbar to Laravel?
Replace `yiisoft/yii2-debug` with `barryvdh/laravel-debugbar` via Composer. Configure it in `config/debugbar.php` to mirror Yii’s debug settings. Laravel’s debugbar supports SQL profiling, request inspection, and exception tracking out of the box.
Is there a way to use yiisoft/yii2-debug in Lumen (Laravel’s micro-framework)?
No, even Lumen’s middleware-based architecture won’t integrate with Yii’s DebugModule. Lumen lacks Yii’s event-driven components and `Yii::$app` structure, making this package unusable. Stick to Laravel-native debugging tools or framework-agnostic solutions like Xdebug.
Does yiisoft/yii2-debug support Laravel’s Artisan CLI or Task Scheduling?
No, this package is tied to Yii’s `Yii::app()` and `Yii::$container`, which don’t exist in Laravel. For Laravel-specific debugging, use tools like `laravel-shift/blueprint` for CLI debugging or `spatie/laravel-activitylog` for scheduled task monitoring.
Can I extract specific features (e.g., SQL logging) from yiisoft/yii2-debug for Laravel?
While possible, it’s not recommended due to high maintenance overhead. Laravel already offers optimized alternatives like `barryvdh/laravel-debugbar` for SQL logging or `beberlei/assert` for runtime assertions. Porting Yii-specific features would require rewriting core logic.
What Laravel packages are alternatives to yiisoft/yii2-debug?
For Laravel, use `barryvdh/laravel-debugbar` (SQL, requests, exceptions), `tightenco/ziggy` (route debugging), or `spatie/laravel-activitylog` (audit trails). For production debugging, consider `tideways/xhprof` or `blackfire/php` for performance profiling.
How do I configure yiisoft/yii2-debug in Laravel’s service providers?
You can’t. This package doesn’t support Laravel’s `ServiceProvider` or `register()`/`boot()` methods. Laravel’s debugging tools integrate directly via middleware or config files, while Yii’s DebugModule requires `Yii::$app`, which doesn’t exist in Laravel.
Will yiisoft/yii2-debug slow down my Laravel application in production?
Even if it worked, this package is optimized for Yii’s event system and would introduce unnecessary overhead in Laravel. Laravel’s debugging tools (e.g., `laravel-debugbar`) are designed to be lightweight and production-safe when configured properly.
Are there any framework-agnostic debugging tools I should use instead?
Yes. For cross-framework debugging, use Xdebug with IDEs like PHPStorm or tools like Blackfire, Tideways, or New Relic. These work with any PHP application, including Laravel, without framework-specific dependencies.
Weaver

How can I help you explore Laravel packages today?

Conversation history is not saved when not logged in.
Prompt
Add packages to context
No packages found.
davejamesmiller/laravel-breadcrumbs
artisanry/parsedown
christhompsontldr/phpsdk
enqueue/dsn
bunny/bunny
enqueue/test
enqueue/null
enqueue/amqp-tools
milesj/emojibase
bower-asset/punycode
bower-asset/inputmask
bower-asset/jquery
bower-asset/yii2-pjax
laravel/nova
spatie/laravel-mailcoach
spatie/laravel-superseeder
laravel/liferaft
nst/json-test-suite
danielmiessler/sec-lists
jackalope/jackalope-transport