- Is rz/field-type-bundle compatible with Laravel?
- No. rz/field-type-bundle is a Symfony 2 bundle, not a Laravel package; it registers through AppKernel and a Symfony DependencyInjection extension, which Laravel does not load. Laravel's closest analogue is a ServiceProvider with register() and boot(), a different contract with different config and discovery semantics. There is no adapter that makes it run inside Laravel without reimplementation.
- How do I install rz/field-type-bundle in a Laravel app?
- You cannot install it as a normal Laravel dependency. Its Symfony 2.x constraints create an unresolvable Composer graph on supported PHP 8.1+ runtimes, and even a forced install would not boot inside Laravel's Application. The practical path is to read the source, extract any domain rules, and rebuild them natively in Laravel.
- What Symfony version does rz/field-type-bundle require?
- The assessment identifies it as a Symfony 2 bundle pinned to Symfony 2.x, including full-stack components such as HttpKernel, DependencyInjection, Form, and EventDispatcher. Symfony 2.8 has been end-of-life since 2018 and 2.3 since 2017. Those versions do not resolve against the Symfony 6 or 7 components used by supported Laravel releases.
- Does rz/field-type-bundle work on PHP 8.1 or PHP 8.2?
- Not reliably. The code is described as PHP 5.x-era, with constructs like each(), dynamic properties, and implicit nullable parameters that fatal or deprecate on PHP 8.1 and later. Even where syntax errors are patched, the Symfony 2 kernel and container will not run inside Laravel. Treat it as incompatible with modern PHP for anything beyond source reading.
- Is rz/field-type-bundle maintained or archived?
- It is effectively unmaintained: the repository is archived, has zero stars, zero dependents, and no active maintainer. That means no issue triage, no security patching, and no upgrade path. Any CVE in its Symfony 2 transitive dependencies stays unpatched permanently.
- Can I use rz/field-type-bundle in production?
- The assessment recommends against production use. The bundle is archived and pinned to end-of-life Symfony 2, so it receives no security or compatibility fixes. Its capability surface is also unverified, and there are no tests to characterize behavior. Use it only as a reference implementation, not as a dependency.
- What does rz/field-type-bundle actually do: field registry, rendering, or validation?
- The README excerpt is empty, and the assessment flags that FieldType bundles often mix a field-type registry with rendering, validation, persistence mapping, and serialization. You must audit the source to determine whether the logic is a benign registry or interleaved with Symfony container lookups and Form events. That distinction determines whether porting is a small registry rewrite or a much larger migration.
- Are there tests or documentation for rz/field-type-bundle?
- There is no test signal, and the README excerpt provides no documentation. Behavior must be characterized directly from source rather than verified from a suite. Check composer.json for version constraints and license terms before reusing any code.
- How would I port rz/field-type-bundle concepts to Laravel?
- Map the Symfony concepts to Laravel: use a ServiceProvider plus config/field_types.php for registration, bind a FieldTypeRegistry singleton or use a manager/driver pattern, define a FieldType contract with validation and normalization, and render with Blade components or views per type. Express validation through Laravel Validator rules or Rule objects, and handle persistence with Eloquent attribute casts. A timeboxed audit first will tell you which field types and side effects actually need porting.
- What are the best Laravel alternatives to rz/field-type-bundle?
- Evaluate maintained Laravel-native options rather than a Symfony 2 bundle: filament/forms for admin form building, spatie/laravel-data with Laravel validation for structured data, novius/laravel-form-builder for form definitions, or a small custom field-type registry. Each integrates with ServiceProviders, Blade, and Laravel's validator out of the box. Compare their field type coverage against your audit before choosing.