Events Log Laravel Laravel Package

Getting Started

• Confirm compatibility before upgrading. v3.7.0 supports Laravel 11.x, 12.x, and 13.x. The minimum Laravel version is now ^11.0, so Laravel 10 applications must either stay on an earlier 3.x release or upgrade Laravel first.
• Install or upgrade with Composer. Use composer require <vendor>/<package>:^3.7 for a new install, or composer update <vendor>/<package> for an existing one. Commit the resulting composer.lock.
• Look first at the package's service provider and published config. These are the primary integration points for a standard Laravel package. Check the package README for the exact provider class, config tag, and facade name.
• First use case: publish the config (php artisan vendor:publish --provider="Vendor\Package\PackageServiceProvider" or the documented tag), set the required values in .env, then resolve the package's main class from the container or call its facade in php artisan tinker to confirm the wiring before building features on top of it.

Implementation Patterns

• Prefer constructor injection over facades. Resolve the package's contracts or main classes through Laravel's container so tests can swap implementations. Use facades only in controllers or views where brevity matters.
• Keep configuration environment-driven. Put deployment-specific values in .env and reference them from the published config file. Run php artisan config:cache in production and php artisan config:clear during local changes.
• Register HTTP integration in the Laravel 11+ style. If the package ships middleware, add it in bootstrap/app.php rather than the older HTTP kernel. Confirm the package's documented middleware alias before registering it.
• Queue long-running work. If the package dispatches jobs or events, run a queue worker and monitor failed jobs. Use Queue::fake() and Event::fake() in tests to isolate package side effects.
• Test against the supported Laravel matrix. Add CI jobs for Laravel 11, 12, and 13. This release explicitly adds Laravel 13 support, so a matrix is the safest way to catch version-specific regressions.
• Use the package's Docker image to reproduce maintainer CI. The release updates the development container to PHP 8.5 and Composer 2.10.0. This is useful when debugging dependency resolution or running the package's own test suite, but it is not a hard runtime requirement for your application.
• Extend through published config and container bindings. Avoid editing vendor files. Bind custom implementations against the package's interfaces or use documented events/macros as extension points.

Gotchas and Tips

• Laravel 10 is no longer supported. This is the main breaking change in v3.7.0. If composer update is blocked, run composer why-not <vendor>/<package> 3.7 to identify the conflicting constraint.
• The Docker PHP 8.5 and Composer 2.10 versions are development-environment details. Your application may run on an older PHP version still supported by Laravel 11–13. If local and CI environments differ, pin config.platform.php in composer.json to avoid resolving different dependency sets.
• Composer 2.10 can resolve differently from older Composer versions. When debugging a dependency conflict, update in a clean environment with composer update --with-all-dependencies rather than only bumping the package.
• Config cache traps are common after upgrades. After publishing new config stubs or changing .env, run php artisan config:clear locally and re-run config:cache during deployment.
• Avoid vendor:publish --force blindly. It overwrites local config changes. Publish once, then diff new config stubs against your modified copy on each upgrade.
• Dev dependency updates do not affect production installs. They only matter if you run or contribute to the package's test suite. Use the updated Docker image for that workflow.
• Debugging checklist: verify the installed version with composer show <vendor>/<package>, confirm Laravel and PHP versions with php artisan about, check package-specific logs if available, and use Laravel Telescope or the log channel to inspect package events and exceptions.