Laravel Database Migrate Test Listener Laravel Package

Getting Started

This package is the shared base layer used by laravel-base projects. Release 3.1.0 is a compatibility release: it moves the package onto Laravel 9 so laravel-base projects can upgrade. There are no advertised new APIs, so treat 3.1.0 as the Laravel 9-compatible line rather than a feature release.

Start by confirming your application targets Laravel 9 and PHP 8.0.2+ (Laravel 9’s minimum). Require the package at ^3.1, then inspect the package service provider and published config first — those define the defaults your laravel-base project inherits. The first practical use case is bootstrapping or upgrading a laravel-base project: publish config and migrations, run php artisan migrate, then exercise a known route or artisan command to confirm the package is wired correctly.

Implementation Patterns

• New laravel-base project: require the package, publish its config/assets/migrations, run migrations and seeders, then layer application-specific code in app/ rather than editing vendor files.
• Existing project upgrade: bump laravel/framework to ^9.0 and this package to ^3.1, run composer update, resolve dependency conflicts, republish config with a diff against the existing file, run migrations, clear caches, and run the test suite.
• Day-to-day usage: consume the package’s base classes, traits, helpers, or service bindings from application code; keep overrides in application-level subclasses or config rather than modifying the package.
• Configuration: drive package behaviour through environment variables and config/*.php; avoid hard-coding values that differ between local, staging, and production.
• CI: test against PHP 8.0/8.1 and Laravel 9, and run php artisan test plus a fresh-install migration check to catch base-project scaffolding issues.

Gotchas and Tips

• Laravel 9 is the compatibility boundary. Do not apply 3.1.0 to Laravel 8 or older laravel-base branches. Check composer why-not laravel/framework 9 if the update will not resolve.
• Laravel 9 ecosystem shifts matter. Flysystem 3, Symfony Mailer, anonymous migration class names, and the lang directory move can expose assumptions in older base-project code. Test file storage, mail, and migrations explicitly.
• Publishing can overwrite. vendor:publish --force will replace customized config or views. Publish once, commit the result, and diff after upgrades.
• Config caching hides changes. Run php artisan config:clear after publishing or changing package config, especially in local and CI environments.
• Debugging: use php artisan about, composer why-not, application logs, and php artisan vendor:publish --list to confirm provider discovery and publishable assets.
• Extension points: prefer published config, overridable views, container bindings for package contracts, and package events/listeners over patching vendor code.