- Is kitlabs/kit-form-bundle a Laravel package?
- No. Despite being catalogued alongside Laravel and PHP packages, it is a Symfony form-type bundle. It ships no Laravel service provider, no config/app.php registration path, and no extra.laravel Composer metadata. If your target is Laravel, treat the repository as reference code rather than a dependency.
- How do I install kitlabs/kit-form-bundle with Composer?
- You would install it with composer require kitlabs/kit-form-bundle, but only in a Symfony 3.x or 4.x-era application with Twig available. You must register the bundle in your kernel or bundles.php, and there is no Laravel package auto-discovery. Check the declared PHP and Symfony constraints in composer.json before attempting an install.
- What form field types does Kit Form Bundle actually provide?
- It provides a FulltextType that binds the Baidu UEditor or UMEditor rich-text widget and a LaydateType that binds the layui laydate date picker. The rest of the package is templates and asset wiring needed to render those widgets. It contributes nothing to domain modelling, persistence, or API concerns.
- Does Kit Form Bundle support Laravel 10, Laravel 11, or newer Symfony versions?
- There is no Laravel support at all, and a Symfony 3/4-era bundle will not install cleanly on Symfony 5, 6, or 7. Expect conflicts around Twig versions and asset-pipeline assumptions. Confirm the exact version constraints in composer.json before planning any work.
- Does the bundle vendor the UEditor and laydate JavaScript assets?
- This is unclear from the available material and should be verified before adoption. If assets are not vendored, you must independently source and pin UEditor or UMEditor and laydate builds. Either way, you are inheriting the lifecycle risk of upstream projects that are no longer actively maintained.
- Is Kit Form Bundle safe for production, given UEditor upload endpoints?
- Legacy UEditor connector endpoints have a documented history of arbitrary file upload and remote code execution issues. Any upload handler included in this bundle is a blocking security review item, not a nice-to-have. If you vendor the code, delete or fully rewrite the upload path, and do not use it as-is on customer-facing surfaces.
- What are good alternatives to Kit Form Bundle for rich text and date inputs?
- For rich text, use a maintained editor such as Tiptap, Quill, or CKEditor 5. For dates, use flatpickr or the native input type=date. In Laravel, implement these with Blade components or form macros, using this bundle only as a checklist for CJK toolbar options and date-format conventions.
- Is kitlabs/kit-form-bundle actively maintained?
- Maturity signals are negligible: roughly 4 stars, 0 dependents, and a composite score of 0.02 against an opportunity score of 2.82. The underlying need for CJK rich-text and date input is real and recurring, but almost nobody has validated this implementation. Check the license file and commit cadence over the last 24 months before relying on it.
- Can I configure the UEditor toolbar, laydate date format, and locale without forking?
- This is an open question for the maintainer and should be confirmed before you commit. You need to know whether option defaults cover toolbar layout, locale, date format, and min/max dates. The package appears oriented toward zh-CN, so verify whether internationalisation is parameterised.
- Should I introduce a Symfony bridge to use Kit Form Bundle inside Laravel?
- No. Adding a Symfony bridge to a Laravel application for two form widgets is not a sensible trade-off. Either replace the widgets with native Laravel and maintained JavaScript libraries, or fork the bundle and re-implement the types against Laravel's form and Blade conventions. Lifting the default option arrays and markup patterns is the only part worth salvaging.