- Is jean-beru/pipeline-bundle a Laravel package?
- No. jean-beru/pipeline-bundle is a Symfony bundle built around Symfony's kernel and dependency-injection lifecycle, including a DI extension and compiler pass. Laravel uses some Symfony components but does not implement the bundle abstraction, so the auto-discovery and service tagging that justify the dependency do not run in a Laravel app.
- Does jean-beru/pipeline-bundle support Laravel 10 or Laravel 11?
- There is no official Laravel version support. The package targets Symfony 6/7 and its own PHP floor, and it ships no Laravel service provider or facade. In a Laravel app you would only get the pipeline classes and would have to write all container integration yourself.
- What is the difference between jean-beru/pipeline-bundle and Illuminate\Pipelines?
- The bundle registers pipes through Symfony service tagging and a compiler pass so named pipelines are assembled at compile time. Laravel's Illuminate\Pipelines\Pipeline is a first-class primitive with through(), send(), then(), and Pipe::carry()/finally() conventions. The functional gap is effectively zero, and the one thing the bundle solves, container-driven pipe registration, is already handled by Laravel's service container and app->tag().
- How do I install jean-beru/pipeline-bundle?
- For Symfony you would run composer require jean-beru/pipeline-bundle and register the bundle in config/bundles.php. In Laravel there is no bundle registration step, so installation would leave you with unused Symfony wiring. You would need to vendor or manually instantiate the pipeline classes, which is not recommended.
- What are the best alternatives to jean-beru/pipeline-bundle for Laravel?
- For Laravel, use the native Illuminate\Pipelines\Pipeline class. If you need framework-agnostic code, league/pipeline is the established fallback. Both cover the composable multi-step workflow use case without adding a Symfony-only dependency.
- Is jean-beru/pipeline-bundle actively maintained?
- Maintenance signals are weak: one star, zero dependents, a single maintainer, and a last release on 2024-03-08. There is no evidence of downstream production usage, no known security policy, and no issue-triage signal. Adopting it means your team becomes the maintainer of record on day one.
- Can I use a Symfony pipeline bundle in a Laravel application?
- It is technically feasible but not worthwhile. One path is to write a Laravel service provider that manually maps tagged services to pipes, which is roughly a 2 to 4 day spike plus permanent ownership. The other path is to instantiate the pipeline classes directly and pass pipe arrays, at which point you have reimplemented Illuminate\Pipelines with extra steps. Do not integrate.
- How do I test pipelines built with jean-beru/pipeline-bundle?
- There is no documented testing story or known test coverage for the bundle. In a Laravel context you would test each pipe as an isolated callable and test the composed pipeline with Illuminate\Pipelines. If you insist on evaluating the bundle, timebox a spike and run parity tests against the native pipeline on three real cases.
- Is jean-beru/pipeline-bundle safe to use in production?
- Technical risk is high, and mostly non-technical: the code may be fine, but nothing validates it. Low adoption, a single maintainer, no security policy, and an old release mean no production stress test exists. For a Laravel production app, standardize on the native pipeline instead.
- Should I use a pipeline pattern in Laravel, and how?
- Yes, the pipeline pattern is useful in Laravel, but use Illuminate\Pipelines\Pipeline rather than a Symfony bundle. A typical call is app(Pipeline::class)->send($payload)->through([...])->then(fn ($p) => ...). If you want declarative named pipelines in config, build a thin in-house layer over Illuminate\Pipelines with a config/pipelines.php registry, about 150 lines that your team fully owns.