Laravel Common Laravel Package

Getting Started

• v1.1.0 is a compatibility release: it adds Laravel 5.3 support. Treat it as a maintenance upgrade unless you are running an L5.3 application that needs this package.
• Look first at the package README, composer.json constraints, service provider, facade/alias registration, and any publishable config. On Laravel 5.3 there is no package auto-discovery, so manual provider registration is expected.
• Minimal install path:
  • Require ^1.1 in the legacy app.
  • Register the service provider in config/app.php.
  • Register any facade alias if the package exposes one.
  • Publish config if available and set environment-specific values.
  • Clear config/cache and smoke-test one real call from a route, controller, or Artisan command.

Implementation Patterns

• For Laravel 5.3 apps, pin to ^1.1 and verify PHP/dependency constraints before rolling out. This release is most useful as an enabler for legacy applications, not as a feature upgrade.
• Keep package usage behind a small application service or existing container binding. That makes it easier to test, swap, and isolate if the package API changes later.
• Use the published config file as the primary integration point. Prefer env-driven config over hard-coded values so local, staging, and production behavior stays consistent.
• Add one integration test or smoke command that boots the provider and exercises the package’s main entry point. This catches missing provider registration, bad config, and container-resolution failures early.
• For newer Laravel versions, there is no indicated API change in v1.1.0. Keep existing usage unless Composer resolution requires the update.

Gotchas and Tips

• Laravel 5.3 does not support package auto-discovery. A missing provider entry typically shows up as “class not found” or an unresolved container binding.
• After publishing or editing package config, run php artisan config:clear. If config caching is enabled, changes may appear to be ignored.
• The release note only confirms L5.3 support; it does not announce new features, breaking changes, or deprecations. Do not assume new APIs from this release.
• Check transitive dependencies carefully. “Supports L5.3” does not guarantee every optional feature or integration works on L5.3.
• Debug provider and binding issues with php artisan tinker, container resolution checks, and a clean config cache. Use the package’s config, facade, or contracts as extension points rather than editing vendor files.