Laravel Vendor Minify Laravel Package

Getting Started

This release adds Laravel 6 support, so the package is now usable on ^5.x and ^6.0 applications. Start by confirming your constraint resolves cleanly:

composer require vendor/package:^1.0.3

If you are on Laravel 6 and were previously pinned to a dev- branch or a 1.0.x-dev alias for compatibility, drop the alias and re-resolve so you get the tagged release rather than a stale lock entry.

First steps, in order:

1. Read the README's Laravel 6 section first — the release note is terse, but the changelog/README usually carries the real detail (minimum PHP bumped to 7.2, any renamed config keys, any dropped helper usage).
2. Check package discovery — php artisan package:discover should list the service provider. If it does not, the provider is not registered in composer.json extra.laravel.providers and you will need to add it to config/app.php manually.
3. Publish and diff the config — php artisan vendor:publish --provider="Vendor\Package\PackageServiceProvider" --tag=config. If you already had a published config from a 5.x install, diff it against the new stub rather than overwriting; the Laravel 6 release may have added keys.
4. Smoke test in Tinker — resolve the package's main entry point from the container and run the simplest read operation before wiring anything into a controller or job.

The first realistic use case is a single read path: one config entry, one facade/contract call, one assertion in a feature test. Get that green before touching queues or caching.

Implementation Patterns

Resolve from the container, do not new it up. Anything the package registers should be pulled via constructor injection or app(). This matters more on Laravel 6 where the container's contextual binding behaviour changed slightly; hand-instantiated objects bypass config and will silently use defaults.

Config over code for environment variation. Keep credentials, endpoints, and driver selection in config/package.php and reference them through env() only inside that file. In application code, read config('package.key') — never env() directly, or config:cache will hand you null in production.

Wrap write paths in jobs. If the package performs network I/O, push it behind a queued job with $tries and $backoff set explicitly. The package's own retry logic (if any) is usually unaware of your queue's retry_after, and the two stacking is a common source of duplicate work.

Test with a swap or fake. Bind a test double over the package's contract in your TestCase::setUp rather than hitting the real dependency. If the package ships a fake()-style helper, prefer it — it usually records calls in a way the real implementation does not.

Compose via events. For side effects after a package operation, listen for the events it dispatches instead of subclassing its internals. Subclassing couples you to private methods that are the most likely thing to change in a patch release.

Register your own driver if the package supports it. Most Laravel packages of this shape expose a manager with an extend() method. Custom drivers registered in a dedicated service provider keep your overrides out of AppServiceProvider and survive upgrades.

Gotchas and Tips

• PHP floor moved. Laravel 6 requires PHP ^7.2. If your CI matrix still has 7.1, the release will not install — the error surfaces as an unrelated symfony/* conflict, so read the full Composer output, not just the last line.
• config:cache is the classic trap. Publish your config, then run php artisan config:cache once in staging before you trust a deploy. Any env() call outside a config file becomes null at that point and nowhere else.
• Package discovery can be stale. After upgrading, run composer dump-autoload and php artisan package:discover. A cached bootstrap/cache/packages.php from the 5.x install will keep the old provider list.
• Check the lock before blaming the package. composer why-not vendor/package 1.0.3 is faster than guessing which transitive illuminate/support constraint is holding you back.
• Helper functions. Laravel 6 deprecated a number of global string/array helpers in favour of Str:: and Arr::. If the package (or your own code calling into it) relies on the globals, you will get deprecation noise now and breakage later.
• Debugging silently-swallowed failures. If the package catches exceptions internally, temporarily point its log channel at a dedicated file (config('logging.channels.package')) so its output is not buried in your application log.
• Extension points to prefer, in order: config → events → custom driver → container binding override. Reach for a bind() replacement last; it is the one that breaks without a visible error when the package adds a constructor argument.
• Pin to ^1.0 rather than ~1.0.3. This release is additive, but patch releases in the 1.0.x line have historically been the ones carrying compatibility fixes — locking to a single patch means missing the next Laravel minor-version fix.