Weave Code
Http Server Laravel Package
hyperf/http-server
Hyperf HTTP Server provides a high-performance, coroutine-based HTTP server for the Hyperf framework, built on Swoole or Swow. It offers PSR-7/PSR-15 middleware support, powerful routing, annotation-driven controllers, and fast request handling for scalable PHP microservices.
🚀 A coroutine framework that focuses on hyperspeed and flexibility. Building microservice or middleware with ease.
Frequently asked questions about Http Server
- Can I install hyperf/http-server in a Laravel application?
- No, not as a Laravel integration. It has no service provider, facade, publishable config, or bindings into Laravel's HTTP kernel, router, middleware pipeline, or container. It is the HTTP server component of Hyperf and assumes Hyperf's coroutine-aware PSR-11 container, Config, EventDispatcher, and Server abstractions. Dropping it into Laravel would mean running a second application kernel, which is an architecture change rather than a Composer install.
- What is hyperf/http-server actually used for?
- It powers HTTP request handling inside the Hyperf framework, built on Swoole or Swow coroutines. It provides PSR-7 request and response objects, a PSR-15 middleware pipeline, annotation-driven controllers, routing, lifecycle events, and pluggable exception handlers. In practice it is a default dependency when you build a Hyperf service, not a package you select independently.
- Does hyperf/http-server support Laravel 10 or Laravel 11?
- There is no Laravel version support because there is no Laravel integration layer. The package is versioned and released with the Hyperf monorepo, and v3.2.0 requires PHP 8.2 or newer. Laravel compatibility is therefore not a meaningful matrix; evaluate it against Hyperf's runtime requirements instead.
- How do I install and configure hyperf/http-server?
- You install it as part of a Hyperf application via Composer, normally through the Hyperf skeleton and framework dependencies rather than as a standalone package. Configuration is handled through Hyperf's config system and server settings, not Laravel-style publishable config files. There is no service provider to register and no facade to alias; the framework bootstrap wires the server and dispatcher.
- Is hyperf/http-server a drop-in replacement for Laravel Octane?
- No. Octane accelerates Laravel's existing synchronous request lifecycle using Swoole, RoadRunner, or FrankenPHP while keeping Laravel's kernel, router, container, and middleware. hyperf/http-server belongs to a different framework with a coroutine-scoped runtime and Hyperf's own container and lifecycle. If your goal is performance for a Laravel app, Octane is the native, lower-risk option.
- What are the production risks of adopting hyperf/http-server?
- The main risk is architectural: you must run Hyperf's coroutine runtime and container alongside or instead of Laravel's synchronous per-request model. The v3.2.0 release is a hard-breaking minor with PHP 8.2 or newer, Carbon v3 semantic changes, config restructuring for logger and cache, async-queue renames, and Symfony 6 removals. Those changes land framework-wide, and the component has no independent changelog or versioning, so you review the monorepo train rather than a focused package.
- How do I test an HTTP server built with hyperf/http-server?
- Testing happens within Hyperf's testing utilities and coroutine-aware application bootstrap, not with Laravel's HTTP test helpers. You assert against PSR-7 responses and exercise the PSR-15 middleware pipeline and routed controllers in a Hyperf test case. Because the runtime is long-lived and coroutine-scoped, tests must respect context isolation rather than assuming a fresh PHP-FPM process per request.
- What alternatives should a Laravel team consider instead of hyperf/http-server?
- For Laravel applications, Laravel Octane is the closest performance alternative and stays native to the stack. RoadRunner or FrankenPHP can also front a Laravel app without replacing its kernel. If you genuinely need Hyperf's coroutine model, adopt Hyperf as a separate service and treat hyperf/http-server as an incidental default dependency, not a drop-in package.
- Is hyperf/http-server actively maintained and safe to depend on?
- Maintenance follows the Hyperf monorepo, so releases are framework-wide and this component has no independent surface or separate review. The provided assessment notes weak adoption signals for the package itself, including very low stars, an unspecified repository, and a composite score around 13. That does not mean the code is unmaintained, but it does mean you are betting on the Hyperf framework as a whole rather than on independent community validation of this component.
- What PHP and driver requirements does hyperf/http-server have?
- Hyperf v3.2.0 requires PHP 8.2 or newer and runs on either the Swoole or Swow coroutine driver. Swow users must bind ResponseEmitterInterface manually, and misconfiguration there is silent. If you target PHP 8.4, account for the fgetcsv and fputcsv escape parameter changes noted in the release.
Weaver
How can I help you explore Laravel packages today?