Laravel Recursive Collection Laravel Package

Getting Started

• Confirm your application is on Laravel 6 or 7. Laravel 7 requires PHP >= 7.2.5, so verify your runtime before upgrading.
• Require the v2.1 line so Composer can resolve illuminate/support as ^6.0 || ^7.0.
• First place to look: the package’s composer.json, service provider registration/auto-discovery, and any publishable config or migrations.
• First use case: upgrade an existing Laravel 6 app to Laravel 7, or install the package into a Laravel 7 app and run the package’s primary workflow in a smoke test.

Implementation Patterns

• Pin the package to ^2.1 when you need Laravel 7 support; keep ^2.0 only for Laravel 6 apps that are not yet upgrading.
• Upgrade with composer update vendor/package --with-dependencies and commit the resulting composer.lock.
• Rely on Laravel package auto-discovery where available, but explicitly verify the provider is registered if your app disables discovery.
• Publish config/assets only when needed, then keep environment-specific values in .env or app config rather than editing vendor files.
• Add a small integration test that boots the package provider, resolves any container bindings/facades, and exercises the main package workflow under Laravel 7.
• Use a CI matrix for Laravel 6 and Laravel 7 if the package is shared across multiple apps.

Gotchas and Tips

• The release only calls out the illuminate/support constraint. Check transitive Illuminate/Symfony dependencies if Composer resolution fails.
• Laravel 7 moves to newer Symfony components; test package behavior that touches HTTP, console, events, or queue internals.
• No breaking changes are indicated in v2.1.0, but treat it as a compatibility release and still run your app’s test suite.
• Clear caches after upgrading: php artisan config:clear, php artisan cache:clear, and php artisan package:discover where relevant.
• If something fails only in Laravel 7, compare resolved dependency versions first; dependency conflicts are more likely than package API changes in this release.
• Use published config and documented extension points instead of modifying vendor code, especially when preparing for future framework upgrades.