Weave Code
Laravel Debug Console Laravel Package
madewithlove/laravel-debug-console
Laravel Debug Console adds an in-app console to your Laravel application, letting you inspect debugging output, logs and runtime details right in the browser. A lightweight alternative to external tools for local development and troubleshooting.
Laravel debugging via the console a viewer for the information collected by Laravel Degubar.
Frequently asked questions about Laravel Debug Console
- What is Laravel Debug Console used for?
- Laravel Debug Console provides a lightweight, browser-based console for inspecting application state, debugging output, logs, runtime details and captured SQL queries without leaving your Laravel app. It is intended for local development and staging/troubleshooting workflows rather than production runtime use. It fits as a developer-facing observability tool installed as a require-dev Composer package.
- How do I install madewithlove/laravel-debug-console?
- Install it with Composer as a development dependency using require-dev, then let Laravel package auto-discovery register the service provider. Publish the package config if offered so you can control access and environment gating. Explicitly restrict registration to local and staging/CI environments through APP_ENV checks or the package's own enable flag. Release 1.0.3 is a narrow rendering patch with no migration or config changes implied.
- Is Laravel Debug Console safe to run in production?
- No, it is intended for development and staging environments, and it should be explicitly excluded from production bootstrapping. Install it under require-dev and gate registration with APP_ENV checks or the package enable flag. Query capture can include bound parameters that may contain credentials, tokens or PII, which is the main compliance exposure. Do not treat configurable access as a substitute for keeping the console out of production.
- Which Laravel and PHP versions does Laravel Debug Console support?
- The assessment assumes a conventional Laravel 10, 11 or 12 application on PHP 8.1+ with Composer and package auto-discovery. Verify the package's actual Composer constraints against your fleet's oldest maintained service before rollout. There are no infrastructure, queue or storage requirements implied by the package.
- Does Laravel Debug Console replace Laravel Telescope or Debugbar?
- It complements rather than replaces existing debugging tools, and teams already using Telescope or Debugbar should treat it as optional. Pick one query-inspection surface, because running two query listeners doubles overhead and can confuse developers about which UI to trust. Verify listener collisions and route or middleware namespace clashes in the dev route group before standardizing.
- Does Laravel Debug Console show query bindings and sensitive data?
- Query capture usually includes bound parameters, and bindings can contain credentials, tokens and PII. That is the primary data-handling risk, more important than layout issues. Check whether the package offers redaction or an opt-out before rolling it out to shared staging environments. Decide on binding visibility and redaction as part of your adoption review.
- How do I control who can access the Laravel Debug Console?
- The package provides configurable access and environment-aware usage, so publish its config if offered and set the access rules deliberately. Gate service-provider registration to non-production environments using APP_ENV checks or the package enable flag. Restrict access further on shared staging systems where query data may include sensitive bindings.
- Is the Laravel Debug Console queries table safe from XSS?
- Confirm that the renderer escapes HTML, because query strings frequently contain user-supplied values and an unescaped queries table is a stored-XSS vector in shared staging environments. Version 1.0.3 fixes overflow from long unbroken strings by hard-cutting overlong tokens with word-wrapping, which is a cosmetic robustness patch. Validate escaping yourself and check whether truncation length is configurable. Also test the hard-cut behavior with UTF-8 and multibyte SQL text.
- How do I test Laravel Debug Console in staging or CI?
- Spike it in a single non-critical service: install as a dev dependency, publish config if needed, and confirm the queries table renders correctly, including the previously breaking long-string case. Test worst-case query text such as large IN clauses, JSON columns, base64 media, JWTs and minified SQL. Validate HTML escaping and binding visibility, then decide on redaction before any shared-environment rollout. Check whether truncated query text remains usable for copy-to-clipboard reproduction workflows.
- Is Laravel Debug Console actively maintained?
- Release 1.0.3 is a cosmetic patch on a 1.x package, which suggests a relatively young project rather than a long-established one. Check maintainer count, release cadence and open-issue volume before standardizing it across teams. Also review support for your Laravel and PHP matrix and whether fixes for escaping or truncation are documented. Treat maintenance signals as part of the adoption decision, not just the feature set.
Weaver
How can I help you explore Laravel packages today?