Getting Started

Install the package via Composer: composer require vendor/package:^1.2. The 1.2.0 release is the first to support Laravel 7, so use this version (or higher) on Laravel 7 projects.
Laravel 7’s package auto-discovery will register the service provider and facade automatically. If you’re on a legacy setup, add Vendor\Package\PackageServiceProvider to config/app.php.
Publish any configuration with php artisan vendor:publish --provider="Vendor\Package\PackageServiceProvider" and review the generated config file.
First use case: inject the package’s main service into a controller or resolve it via the facade, then call the primary API as documented in the README. Verify it works on a fresh Laravel 7 install before integrating into existing code.

Implementation Patterns

Version pinning: In composer.json, require "vendor/package": "^1.2" alongside "laravel/framework": "^7.0". This ensures compatibility with Laravel 7’s Symfony 5 dependencies.
Service container: Bind the package’s interfaces in a service provider if you need to swap implementations. Laravel 7’s container is unchanged, so existing patterns still apply.
Facade usage: Use the facade for quick access in controllers, jobs, and Blade views. For testability, prefer constructor injection of the underlying service.
Config-driven behaviour: Publish the config and use environment variables to toggle features. Laravel 7’s config caching works as expected—run php artisan config:cache after changes.
Artisan commands: If the package provides commands, they are auto-registered. Use them in deployment scripts or scheduled tasks via Laravel 7’s scheduler.
Testing: Use the package’s facade fake or mock the underlying service in your tests. Laravel 7’s testing helpers (e.g., RefreshDatabase, Http::fake) are fully supported.

Laravel version constraint: 1.2.0 requires Laravel 7. If you’re still on Laravel 6, stick with ^1.1. Upgrading? Test the package in a branch first—Laravel 7’s Symfony 5 upgrade can surface transitive dependency conflicts.
Auto-discovery cache: After installing or upgrading, run php artisan package:discover (or composer dump-autoload) to refresh the discovered packages manifest.
Blade components: If the package ships Blade components, Laravel 7’s new component syntax may require adjustments. Check the package’s view namespace and publish tags.
Debugging: Use php artisan tinker to resolve the package service and inspect behaviour. Enable query logging or use Laravel Telescope to trace package interactions.
Extension points: Most Laravel packages expose config, events, and macros. Publish the config, listen for package events, and check for Macroable traits if you need to extend behaviour without forking.
Deprecations: Laravel 7 deprecates some helpers (e.g., str_* and array_* in favour of Str and Arr). If the package’s public API returns strings/arrays, update your usage accordingly.
Upgrade path: Review the package’s CHANGELOG for any breaking changes between 1.1 and 1.2. Since the release note only mentions Laravel 7 support, the API is likely unchanged—but verify with a quick smoke test.