Weave Code
Stacked Dumper Laravel Laravel Package
avto-dev/stacked-dumper-laravel
Laravel integration for avto-dev/stacked-dumper that collects debug dumps into one organized stack, letting you inspect multiple values together instead of scattering var_dump output through the page. A small, framework-friendly utility for cleaner local debugging and easier comparison of dumped dat...
Stacked variables dumper for Laravel-based application
Frequently asked questions about Stacked Dumper Laravel
- What is avto-dev/stacked-dumper-laravel used for?
- It is the Laravel integration for avto-dev/stacked-dumper, a utility that collects multiple debug dumps into one organized stack. Instead of scattering var_dump output across the page, you can inspect several values together in a single place. It is intended for cleaner local debugging and easier comparison of dumped data.
- How do I install avto-dev/stacked-dumper-laravel with Composer?
- Install it with Composer using composer require avto-dev/stacked-dumper-laravel. On Laravel 11 and newer the package service provider is typically auto-discovered, but you should verify bootstrapping after installation. If the package ships configuration, publish it according to the package documentation before customizing behavior.
- Which Laravel versions does stacked-dumper-laravel support?
- The current release requires Laravel ^11.0 and is intended for Laravel 11, 12, and 13 applications. Laravel 10 and earlier are outside the new constraint and will not resolve against this version. Check the package composer.json for the exact illuminate/* requirements before upgrading.
- Does avto-dev/stacked-dumper-laravel work with Laravel 10?
- No, the current release requires Laravel ^11.0, so Laravel 10 applications will fail dependency resolution or need to pin an older package version. Dropping Laravel 10 is a breaking compatibility change even though the package version is only 1.10.0. Applications still on Laravel 10 should schedule a framework upgrade before adopting this release.
- What PHP version do I need for stacked-dumper-laravel?
- The package targets a supported PHP 8.x runtime, but you should confirm the exact platform constraint in its composer.json. PHP 8.5 appears in the project Docker and CI setup and should not automatically be assumed to be the minimum production requirement. Validate against the PHP version your application actually runs in production.
- How do I configure the stacked dumper in Laravel?
- After installing, confirm the service provider is registered or auto-discovered, then publish any package configuration if the documentation instructs you to do so. Adjust the configuration for your local debugging workflow and clear cached config with php artisan config:clear. Run a quick dump to confirm output is collected into a single stack.
- Can I use stacked-dumper-laravel in production?
- It is a debugging tool, so it is best limited to local and development environments. Avoid leaving dump output enabled in production because it can expose sensitive values or clutter responses. Disable or remove the package from production deployments unless you have a deliberate, secure use case.
- How can I test that stacked-dumper-laravel is working?
- Trigger a dump in a local route or test controller and confirm the values appear together in one organized stack rather than at scattered points in the page. After upgrading, run your application test suite and verify service provider bootstrapping and configuration publishing. Also check for dependency resolution errors in CI before rolling out.
- How is stacked-dumper-laravel different from Laravel's dump and dd helpers?
- Laravel's dump helper outputs values inline and dd halts execution immediately. Stacked-dumper collects multiple dumps into one organized stack so you can compare several values side by side without hunting through the page. It complements, rather than replaces, Laravel's built-in debugging helpers.
- Is avto-dev/stacked-dumper-laravel maintained, and how do I upgrade to the latest version?
- The package tracks a current Laravel support matrix covering Laravel 11, 12, and 13, which reduces maintenance for older framework versions. To upgrade, update the Composer constraint, run composer update for the package, and execute your full test suite. Treat the dropped Laravel 10 support as a breaking change and verify PHP and Composer 2.10 compatibility in your CI pipeline.
Weaver
How can I help you explore Laravel packages today?