Laravel Http Sender Laravel Package

Technical Evaluation

Architecture fit: saloonphp/laravel-http-sender is a lightweight Laravel integration that lets Saloon connectors/requests use Laravel’s HTTP client as the sender. It fits Laravel applications already using Saloon that want Laravel-native HTTP behavior, including request mocking, retries, and testing hooks. The v3.1.0 release confirms compatibility with Laravel 12.x and resolves a PHP 8.4 implicit-nullable deprecation, aligning the package with current framework/runtime baselines.

Integration feasibility: Low effort. The package is installed via Composer, auto-discovered in Laravel, and configured as a Saloon sender. No application-level architecture changes are required unless custom senders or HTTP pipelines exist. The v3.1.0 changes are compatibility/deprecation fixes, not API changes.

Technical risk: Low. This is a minor, non-breaking release. The main risk is environmental: teams still on older Laravel or PHP versions may not need v3.1.0 immediately, while teams targeting Laravel 12 or PHP 8.4 should adopt it to avoid deprecation noise and future incompatibility. Dependency coupling with Saloon major versions remains the primary long-term risk.

Key questions:

• Are we currently using Saloon, and do we need Laravel HTTP client integration?
• What Laravel and PHP versions are in production and CI?
• Do we have custom Saloon senders or HTTP client configuration that could conflict?
• Are HTTP interactions covered by tests (mocking, retries, error handling)?
• What is our upgrade timeline for Laravel 12 and PHP 8.4?

Integration Approach

Stack fit: Compatible with Laravel 10/11/12-era applications and PHP 8.4. The package complements Saloon v3 and Laravel’s HTTP client. It is appropriate for teams standardizing on Laravel’s HTTP layer for observability, testing, and retry behavior.

Migration path: From v3.0.0 to v3.1.0 is a drop-in Composer update. No code changes are expected. Teams on older Laravel versions can adopt v3.1.0 without forcing a framework upgrade; teams planning Laravel 12 or PHP 8.4 should include it in the upgrade sequence.

Compatibility: Backwards compatible with v3.0.0. Adds Laravel 12.x support and PHP 8.4 deprecation safety. Confirm that the installed Saloon version and Laravel HTTP client configuration are supported by the package’s Composer constraints.

Sequencing:

1. Update composer.json to saloonphp/laravel-http-sender:^3.1.
2. Run composer update in a branch and review lock-file changes.
3. Execute the full test suite, especially HTTP-mocking and integration tests.
4. Verify no PHP 8.4 deprecation warnings in CI.
5. Deploy to staging before production; no data migration or config changes required.

Operational Impact

Maintenance: Low. The package is actively maintained within the Saloon ecosystem. Minor releases like v3.1.0 indicate ongoing compatibility work. Maintenance effort is primarily dependency tracking: Saloon major versions, Laravel releases, and PHP runtime upgrades.

Support: Community-supported package. Internal teams should designate an owner for HTTP client dependencies and track Saloon/Laravel release notes. Vendor support is not applicable unless covered through an internal platform team.

Scaling: No material scaling concerns. The package delegates HTTP transport to Laravel’s HTTP client, so performance characteristics match the underlying client. Scaling considerations are the same as any outbound HTTP integration: connection pooling, timeouts, retries, and queue/worker capacity.

Failure modes:

• Dependency version mismatch between Saloon, Laravel, and the sender package.
• PHP 8.4 deprecation warnings if older versions remain pinned.
• Network failures, timeouts, or retry exhaustion handled by Laravel/Saloon configuration.
• Unexpected behavior if custom Saloon senders bypass the Laravel sender.
• Future Saloon major-version upgrades may require coordinated package updates.

Ramp-up: Low. Developers familiar with Laravel and Saloon can adopt the package quickly. Documentation is available through Saloon and Laravel’s HTTP client docs. Teams unfamiliar with Saloon should budget time for connector/request patterns and HTTP testing conventions.