Weave Code
View Laravel Package
hoa/view
Hoa\View is a lightweight PHP view layer for composing and rendering templates through view containers. It provides a simple abstraction for presenting data in Hoa-based applications, though the package is largely legacy and minimally maintained.
Hoa\View is a lightweight view layer for PHP from the modular Hoa framework. It defines a simple Viewable contract that decouples rendering from application logic, so controllers stay free of presentation details while dedicated implementations handle output.
Viewableinterface for interchangeable view objects- Built-in HTML and JSON renderers
- Integrates cleanly with Hoa\Dispatcher and routing
- Supports layouts and template composition
- Minimal dependencies and easy to extend
Frequently asked questions about View
- Does hoa/view work with Laravel?
- No, hoa/view has no native Laravel integration. It ships no service provider, facade, configuration, or published assets, and it does not implement Laravel's Illuminate\Contracts\View\Engine contract. Laravel's view pipeline expects an engine that returns a rendered string, while Hoa\View renders through Hoa's own stream abstractions. Using it in Laravel requires a custom adapter you write and maintain yourself.
- How do I install hoa/view with Composer?
- You install it with composer require hoa/view, but expect friction on modern PHP because the last release was in January 2017. Its Composer constraints predate PHP 7.4 and PHP 8.x, so dependency resolution may fail without platform overrides. Including the library also bootstraps Hoa's consistency and autoload layer, and registering the hoa:// stream wrapper is a global side effect. Verify behaviour on your target PHP version rather than assuming it works.
- Is hoa/view compatible with PHP 8 and modern Laravel versions?
- There is no evidence of compatibility with PHP 8 or current Laravel releases. The code was never continuously tested against modern PHP, and the Hoa organisation is archived with no security or version maintenance. Breakage is plausible in removed or deprecated language features and in Hoa's error and exception layer. Any compatibility claim must be empirically verified by running the test suite on your exact PHP version.
- Can I use hoa/view as a Laravel view engine?
- Only through a hand-written compatibility shim that implements Laravel's Engine contract, bootstraps Hoa's consistency and autoload layer, registers the hoa:// protocol stream wrapper, and converts stream output back into a string Laravel can buffer. That is not a wiring exercise; it is a permanent ownership commitment for an abandoned library. The shim would become the only maintained code in the rendering path. Global stream-wrapper registration and Hoa error-handler conventions can also collide with Laravel's error handling.
- Is hoa/view abandoned or still maintained?
- Yes, it is effectively abandoned. The last release was 2017-01-14, the Hoa organisation is archived, and the package has roughly 8 stars and 0 dependents. There is no maintainer to escalate to, no community answers, and no third-party patches. That leaves a bus factor of one for anyone who builds an integration.
- What are the best alternatives to hoa/view for templating in Laravel?
- Blade is Laravel's default and requires zero integration effort. Twig is available through rcrowe/twigbridge, which is maintained and documented, and league/plates offers plain-PHP templating with a PSR-friendly design. Each of these delivers more capability with a fraction of the ownership burden compared with adapting Hoa\View. Prefer them unless a legacy Hoa application forces the choice.
- How is hoa/view different from Blade or Twig?
- Hoa\View is a view abstraction layer, not a template engine in the Blade or Twig sense. It provides an abstract View contract, composition primitives such as aggregate and partition styles, and an HTML renderer built on Hoa's stream stack. Blade and Twig compile templates and integrate directly with Laravel's rendering pipeline. Hoa\View models view composition and stream-based rendering rather than template syntax.
- What dependencies does hoa/view require and can they conflict with Laravel?
- It depends on Hoa's stream stack, including hoa/stream, hoa/protocol, and hoa/file. Those dependencies register a global hoa:// stream wrapper at include time and follow Hoa consistency-layer error-handler conventions. That can collide with Laravel's error handling and with PHPUnit's conversion of errors to exceptions. The dependency chain is also unmaintained, so any conflict has no upstream fix path.
- Will hoa/view break my PHPUnit test suite?
- It can, because its bootstrap is side-effectful. Global stream-wrapper registration and Hoa's error-handler conventions may interfere with PHPUnit's error-to-exception conversion, which is a classic source of flaky suites. Any adapter must be tested in isolation and carefully reset between tests. This risk should be proven or disproven on your target PHP version before adoption.
- Is hoa/view safe to use in production?
- It carries high technical risk: the upstream is abandoned, there is no security response, no PHP-version maintenance, and no maintainer to escalate to. Licensing under BSD-3-Clause is not the blocker; maintenance is. Treat Hoa\View as a research or reference artifact rather than a shipping dependency. If a legacy Hoa application forces the choice, the correct deliverable is a migration plan to a maintained engine, not a permanent adapter.
Weaver
How can I help you explore Laravel packages today?