Product Decisions This Supports

Migration strategy for legacy systems still using react/http-client to react/http, prioritizing technical debt reduction
Build vs buy decision: avoid building new features on deprecated package; adopt react/http for maintainable solution with PSR-7 and Promise-based API
Roadmap planning: allocate resources for upgrading existing services to modern HTTP client standards, ensuring compatibility with current ecosystem practices
Use cases: only applicable for temporary legacy maintenance with strict migration deadlines; never for greenfield projects

When to Consider This Package

Never for new projects – explicitly deprecated with no active maintenance (last release 2021) and 0 dependents
Only for short-term legacy support where immediate migration is impossible (e.g., critical production systems with no downtime window), but with a documented 30-day migration plan to react/http
Look elsewhere for all new development: use react/http (official successor), Guzzle for synchronous use cases, or modern async clients like Amp/Http-Client

Executives: "This package is deprecated and unmaintained. Continuing to use it introduces security risks, blocks modern feature development, and creates technical debt. Migrating to react/http ensures a supported, performant HTTP client with PSR-7 standards and Promise-based async flows – reducing long-term maintenance costs by 70% while future-proofing our infrastructure."
Engineering: "Replace react/http-client with react/http immediately. The new API simplifies requests via $browser->get()->then() syntax, uses Promises for cleaner async flow, and aligns with PSR-7 standards. Migration requires updating Composer dependencies and refactoring event-based patterns to Promise-based – documented examples show 80% fewer lines of code for equivalent functionality."