Php Var Dump Check Laravel Package

Product Decisions This Supports

• Debugging Efficiency: Automates the detection of accidental var_dump, dd, or framework-specific debugging calls left in production code, reducing manual code reviews and improving deployment reliability.
• DevOps & CI/CD Integration: Enables pre-deployment checks in CI pipelines (e.g., GitHub Actions, Jenkins) to block code containing debugging dumps, aligning with "shift-left" testing principles.
• Framework-Specific Compliance: Supports Laravel (dd, dump), Symfony (VarDumper), and other frameworks, ensuring consistency across multi-framework codebases.
• Cost vs. Build: Avoids reinventing a static analysis tool for a common pain point (forgotten debug statements), leveraging an open-source solution with minimal maintenance overhead.
• Onboarding & Best Practices: Standardizes debugging practices by integrating checks into developer workflows (e.g., pre-commit hooks) and reducing "debug dump pollution" in shared repositories.

When to Consider This Package

• Adopt if:
  • Your team frequently ships PHP/Laravel/Symfony applications and struggles with accidental debug statements in production.
  • You lack a dedicated QA process for manual code reviews focused on debugging artifacts.
  • CI/CD pipelines are in place and can enforce pre-deployment checks (e.g., fail builds on forgotten var_dump).
  • You use frameworks/tools like Laravel, Symfony, Tracy, or Doctrine that rely on custom dumping methods.
• Look elsewhere if:
  • Your codebase is small or debug statements are intentionally left in (e.g., feature flags for admins).
  • You require real-time IDE integration (e.g., PHPStorm inspections) instead of CLI-based scanning.
  • The package’s abandonment concerns outweigh the benefits (consider the alternative).
  • You need support for PHP 5.3/HHVM or modern PHP versions beyond 7.2 (though the package is PSR-4 compliant).

How to Pitch It (Stakeholders)

For Executives: "This tool automates the cleanup of debugging code—like var_dump or Laravel’s dd—that often slips into production, causing performance issues or exposing sensitive data. By integrating it into our CI pipeline, we can catch these errors early, reduce post-launch fires, and improve code quality with minimal effort. It’s a low-cost, high-impact fix for a common pain point, especially for teams using Laravel or Symfony."

For Engineering/DevOps: *"We can add a pre-deployment check to block commits/pushes containing forgotten debug dumps. It supports our stack (Laravel/Symfony) and runs in seconds via CLI. Example:

./vendor/bin/var-dump-check --laravel --symfony --exclude tests .

This aligns with our goal to automate manual QA tasks. The alternative is a maintained fork or building our own scanner—this gives us 80% of the value with zero maintenance."*

For Developers: *"No more ‘Why is my API slow?’ mysteries caused by leftover var_dump calls. This tool scans your codebase and flags them—just run it locally or in CI. It even handles Laravel’s dd and Symfony’s VarDumper. Example output:

Forgotten dump 'dd' found in ./src/Controller/UserController.php:42

It’s like a spellcheck for debugging code."*