- Is hoa/core compatible with Laravel?
- No. hoa/core has no Laravel service provider, facade, config publishing, or container awareness, and it was archived in November 2015 targeting PHP 5.4/5.5-era code. It is the bootstrap layer for the separate Hoa framework, so treating it as a Laravel package creates a second bootstrap and error-handler stack rather than an integration.
- How do I install hoa/core with Composer?
- You can run composer require hoa/core, but the last release was 2015-11-09 and the repository is archived. In practice it is usually pulled in transitively by older Hoa packages rather than installed directly. If it appears in your lock file, identify the parent package first because that dependency is the real issue.
- Which Laravel versions support hoa/core?
- None officially. hoa/core predates modern Laravel, PSR-11, and PSR-15, and there is no maintained Laravel bridge. Wiring it into Laravel 8, 9, 10, or 11 would be a bespoke fork owned entirely by your team, not a supported integration.
- What is hoa/core actually used for?
- It provides the Hoa framework bootstrap, shared context and parameter storage, protocol and stream-wrapper registration, consistency assertions, and a common exception hierarchy. It is a foundation for other Hoa libraries, not a standalone utility package. Most projects encounter it indirectly through Hoa dependencies.
- Can I use hoa/core's event bus instead of Laravel's dispatcher?
- You should not. Hoa\Core\Event duplicates Illuminate\Events\Dispatcher, and running both means two event systems in one process. Use Laravel's dispatcher for application events and keep any legacy Hoa event usage isolated to the code that truly requires it.
- Does hoa/core work on PHP 8?
- It is unproven and risky. The package relies on global error handlers, shutdown function registration, and assertion semantics that changed significantly in PHP 7 and 8. Expect deprecation warnings at minimum and hard fatals at worst, so test on your exact PHP version before considering it.
- What are good alternatives to hoa/core in Laravel?
- Use Composer for autoloading, App\Exceptions\Handler for error handling, Illuminate\Events\Dispatcher for events, symfony/options-resolver or Laravel config for parameters, and Flysystem or a small custom stream wrapper for protocols. These are maintained, framework-native, and avoid a parallel runtime. If you need assertions, use a small internal package or a maintained assertion library.
- How do I replace hoa/core in a legacy Laravel project?
- First identify which symbol you actually use, such as Consistency, Event, Protocol, or the bootstrap. Then map each one to a maintained equivalent and scope any remaining behavior into a small internal package. Do not port the whole 2015 framework core just to keep one helper working.
- Is hoa/core maintained and secure?
- No. The repository was archived in November 2015, has roughly 35 stars and no tracked dependents, and has no security response process. Any vulnerability in the code or its transitive tree becomes your team's responsibility to patch forever. That is a high, unhedged supply-chain risk for production.
- How should I test hoa/core in a Laravel application?
- Test it only in an isolated branch or separate process, and verify handler registration order because Hoa\Core installs process-wide error and exception handlers. If it wins the race against Laravel's handler, you can lose framework error reporting, Ignition pages, and structured logging. In most cases the correct test outcome is to reject the dependency and use a maintained alternative.