- What does iter8/builder-bundle actually do?
- It packages the Iter8 builder pattern for PHP applications, giving you fluent, chainable builder classes that centralize complex object and workflow construction, cut duplication, and stay easy to unit test. It adds bundle configuration and services so you can assemble custom components with less boilerplate. It is a PHP-first library, not a Laravel-first one, so treat the framework integration as something you own.
- Can I use iter8/builder-bundle in a Laravel application?
- Not natively. The -bundle suffix is literal: this is a Symfony bundle registered in config/bundles.php, whereas Laravel relies on ServiceProviders, package discovery, and optional Facades. Without bundle registration, any container-coupled behaviour such as service definitions, tagged services, or compiler passes is silently inert. The only viable route is installing it as a plain PHP library and writing your own ServiceProvider and config wiring on top, which means you own the entire integration surface.
- How do I install iter8/builder-bundle with Composer?
- Mechanically it is trivial: composer require iter8/builder-bundle, and PSR-4 autoloading does the rest. The real blockers are the constraint graph and semantics, because a 2023-era release line may pin symfony/* versions that conflict with a modern Laravel app. Test the install against your PHP and Laravel versions before committing to it.
- Which PHP and Laravel versions does iter8/builder-bundle support?
- The package does not target Laravel at all, and there is no documented Laravel support matrix. The latest release is v3.0.1, a single Symfony deprecation fix on a line that dates back to at least August 2023, which predates the Laravel 11 skeleton and current PHP defaults. Verify compatibility yourself rather than assuming a permissive constraint means it will run correctly.
- Is iter8/builder-bundle still maintained?
- It is dormant rather than dead. After a long quiet period, v3.0.1 arrived as a one-line deprecation fix, which signals custodial upkeep or automated tooling rather than active development. There is no roadmap and no evident support commitment, and the response latency appears to be measured in years, which is not something you can plan a release train around.
- What changed in v3.0.1?
- v3.0.1 fixes a single Symfony deprecation, and the full diff from v3.0.0 is one line. It is a genuine positive in that it shows the maintainer tracks Symfony's deprecation cycle, which is exactly the failure mode that hurts most at framework upgrade time. It does not indicate new features or a maintenance commitment, and it is worth confirming whether an intervening major landed between the 2023-08 release and now, since v3.0.0 is not in the public assessment history.
- How should I test this package inside a Laravel app?
- Because the vendor does not test any of the Laravel integration surface, you own it entirely. Write isolated unit tests around your own builder subclasses and an integration test that exercises the real code path inside a Laravel test case. Specifically cover the failure mode where the package autoloads cleanly but silently does nothing without bundle registration.
- What are the production risks of depending on iter8/builder-bundle?
- Two stars and zero dependents means no community validation and no downstream consumers exercising edge cases. With years of dormancy there were no security patches during that gap, and the bus factor is effectively one. If the builder emits SQL or HTML, an unmaintained package will not receive an advisory or a patch when a vulnerability surfaces.
- What alternatives should I consider before adopting this bundle?
- For most Laravel projects, hand-written builder classes, Laravel's own query builder, or a small manager/pipeline pattern cover the same ground with no integration tax. If you need a fluent DTO or payload builder, a compact in-app implementation is usually cheaper and safer than adopting an unmaintained Symfony bundle. Choose this package only if you are already using Iter8 and want consistency.
- Is the builder a query builder, a form/schema builder, or a DTO builder?
- That remains undocumented, and it is the highest-value question left open. A query builder carries a SQL injection surface, a form or schema builder raises DOM escaping concerns, and a DTO builder is largely inert value objects. Each implies a very different blast radius, and the release notes do not address it, so scope the component before you adopt it.