- Is megawilddaddy/formflow-bundle a Laravel package?
- No. It is a Symfony bundle (a fork or mirror of craue/CraueFormFlowBundle) that extends Symfony's Bundle class and registers services through a DependencyInjection extension. It depends on symfony/form, symfony/event-dispatcher, symfony/http-foundation, and the Symfony kernel's bundle bootstrapping. There is no Laravel ServiceProvider, no facade, and no adaptation layer, so nothing about it is Laravel-native.
- Can I install megawilddaddy/formflow-bundle in a Laravel 10 or Laravel 11 application?
- Not in any practical sense. You would either have to pull symfony/form in standalone mode and rewrite the flow state machine and storage adapter yourself, or run Symfony components side-by-side with Laravel's container, which gives you two service containers, two event dispatchers, and two session abstractions. Both paths cost far more than implementing the feature with Laravel primitives, and for a multi-step form that is not a justified trade.
- How do I install and configure the bundle in a Symfony application?
- Install it with Composer, register the bundle in config/bundles.php, define a flow class for each form, and wire up your step templates. That is the standard, well-trodden Symfony path and it works the same way as upstream Craue. Note that the last tagged release on this artifact is 2021-03-01, so verify it against your Symfony version before committing.
- Does this package support PHP 8.2+, Symfony 6, and Symfony 7?
- Unverified and unlikely without work. The last release dates to March 2021, before many of the container compilation and autowiring default changes that landed in later Symfony versions. Symfony bundle conventions changed materially after that baseline, including attribute-based routing and container behavior. Assume no compatibility with current Symfony or PHP until you run a spike to confirm.
- What license is megawilddaddy/formflow-bundle released under, and is it safe for commercial use?
- The package metadata declares NOASSERTION, while upstream CraueFormFlowBundle is MIT licensed. An unverified or altered license declaration is a legal blocker for commercial distribution and a well-known supply-chain red flag. Read the actual LICENSE file in the repository and have legal review it before adoption. Do not assume MIT because the upstream project is MIT.
- Is megawilddaddy/formflow-bundle actively maintained?
- No. The last release is 2021-03-01, there is no security patching, and no Symfony 6/7 or PHP 8.2+ compatibility work has been published. The artifact shows zero stars and zero dependents, so no downstream users are exercising the code paths you would rely on. There is also no identifiable maintainer for this specific fork.
- How is this different from craue/CraueFormFlowBundle?
- The Composer name and the repository URL point at different projects, which strongly suggests a renamed fork or a stale mirror of the upstream bundle. You cannot tell from the metadata whether it is a straight copy, an old snapshot, or a modified fork with unknown changes. Produce a diff against upstream Craue at the 2021-03 baseline and confirm provenance before you evaluate it further.
- What features does the bundle actually provide for multi-step forms?
- It organizes sequential, wizard-style forms: step definitions, per-step validation groups, session-persisted flow data, and transition guards that enforce the order of navigation. The domain model is genuinely sound and is the reason the upstream project is respected. The value is in the flow state machine, not in the Symfony wiring, which is also why the concepts translate cleanly to other frameworks.
- How do I build multi-step forms in Laravel without this bundle?
- Reimplement the flow concepts with Laravel-native primitives: a FormFlow service backed by the session store, a StepRegistry of step definitions, a FormRequest per step for validation, and a controller that resolves the current step and enforces forward-only transitions. A Livewire or Inertia wizard component works well for the UI layer. This preserves the domain model while removing the cross-framework bridge, and it is realistically a one to two sprint effort.
- How should I test a multi-step form flow before shipping it to production?
- Test the state machine directly: assert that each step validates its own group, that session data persists across steps, and that illegal transitions are rejected. In a Laravel implementation, write feature tests that POST each step in sequence, assert redirects, and inspect the session payload. If you do adopt this Symfony bundle instead, budget a spike first, because zero dependents means almost none of these code paths are proven in the wild.