- Is helios-ag/fm-summernote-bundle compatible with Laravel?
- No. FM Summernote Bundle is a Symfony bundle that integrates Summernote through Symfony's Form component, Twig templates, and DependencyInjection extension. It does not ship a Laravel service provider, Blade directive, or any Laravel-specific configuration, so installing it in a Laravel app would pull in Symfony primitives without providing a native integration.
- Can I install helios-ag/fm-summernote-bundle in a Laravel project with Composer?
- You can run composer require helios-ag/fm-summernote-bundle, but Composer will resolve Symfony Form, Twig, Config, and DependencyInjection dependencies that Laravel does not use. The package's service definitions and form type are built for Symfony's kernel and bundle registration, so a Laravel app would not auto-discover or wire them correctly without heavy custom glue.
- What Laravel versions does fm-summernote-bundle support?
- None officially. The 1.0 release targets Symfony 5 and Symfony 6 with PHP 8-era constraints, and its changelog focuses on Symfony bundle configuration, dependency injection, and Twig rendering. Laravel version support is not declared or tested, and the package has no Laravel service provider or facade.
- How do I add Summernote to a Laravel Blade form instead?
- Use a Laravel-native package or implement Summernote directly: include Summernote's JS and CSS via Vite or a CDN, initialize it on a textarea in a Blade component, and handle uploads with a Laravel controller. This avoids dragging Symfony Form, Twig, and DependencyInjection into your Laravel container for a single rich-text field.
- Does fm-summernote-bundle provide a Blade directive or Laravel form macro?
- No. The bundle exposes a Symfony form type called SummernoteType and renders initialization through a Twig template. There is no Blade directive, no Laravel form macro, and no view component, so you would have to rewrite the rendering layer to use it in Laravel.
- Is helios-ag/fm-summernote-bundle still maintained?
- The 1.0 release shows modernization for Symfony 5 and 6, Dependabot automation, and issue templates, but it remains a single-maintainer project with roughly 7 stars and 0 dependents. Maintenance activity is Symfony-focused and does not indicate Laravel support or future Laravel compatibility.
- What are the best Laravel alternatives to fm-summernote-bundle?
- Look for Laravel-specific Summernote packages, or use a general WYSIWYG package like TinyMCE, Trix, or CKEditor integrated through Blade and Vite. For a lightweight path, initialize Summernote manually in a Blade component and store HTML in your model with server-side sanitization.
- Does fm-summernote-bundle support image uploads in Laravel?
- The bundle offers optional file and image uploads through FMElfinder integration, which is a Symfony-oriented finder and connector stack. There is no Laravel filesystem or Storage facade integration, so upload handling would need to be rebuilt with Laravel's filesystem and validation.
- How do I configure Summernote toolbar and height in Laravel?
- In the Symfony bundle, toolbar, height, language, and air mode are set through bundle configuration and passed to the Twig initialization template. In Laravel, you would instead pass those options as a JavaScript object when calling the Summernote initializer inside a Blade component or Vite module.
- Is it safe to use fm-summernote-bundle for production in a Laravel app?
- It is not recommended. The package has no Laravel surface, ships Symfony dependencies, and provides no server-side HTML sanitization, so stored XSS protection remains your responsibility. The asset line also shows legacy signals such as jQuery 2.x compatibility, and the 0.2 to 1.0 jump included an unlabelled config key rename.