- Can I use nicolassing/quill-bundle in a Laravel application?
- No. nicolassing/quill-bundle is a Symfony bundle built around Symfony bundles, dependency injection, and Twig/asset conventions, and Laravel has no equivalent bundle system. Dropping it into Laravel gives you no usable integration; you would end up copying fragments and reimplementing asset loading through Vite and Blade. For Laravel, install Quill from npm and build a Blade component instead.
- How do I install nicolassing/quill-bundle in a Symfony app?
- Install it with Composer, enable NicolassingQuillBundle in config/bundles.php, and include the provided assets and templates where your form or Twig view renders the editor. Because the last release is from January 2021, check the composer.json constraints against your PHP and Symfony versions before committing. If it does not install cleanly on Symfony 6 or 7, forking the small template and asset wrapper is usually cheaper than fighting constraints.
- Does nicolassing/quill-bundle support Laravel 10 or Laravel 11?
- No. There is no Laravel service provider, facade, config publish tag, or Blade integration in this package, and its release history stops in 2021. Laravel 10 and 11 users should treat it as a reference only. Use Quill directly with npm and Vite, or choose a maintained Laravel rich-text package.
- Is nicolassing/quill-bundle a Symfony Form type or just a Twig template?
- The package overview advertises a Symfony form type plus bundled Quill assets and template helpers, but the practical value is a thin wrapper around Quill rendering. Verify the actual source before adopting, because if it is mostly Twig and asset registration, reusing it means copying a few dozen lines. That matters more for Symfony than Laravel, where none of the form-type code applies.
- Do I need to sanitize HTML from a Quill editor before saving it?
- Yes. A WYSIWYG editor produces HTML, and storing unsanitized HTML creates a stored XSS path regardless of whether the editor is Quill, TinyMCE, or Tiptap. nicolassing/quill-bundle does not document server-side sanitization, so do not assume editor output is safe. In Laravel, sanitize with mews/purifier or symfony/html-sanitizer on the server, and treat DOMPurify as defense in depth only.
- What are the best alternatives to nicolassing/quill-bundle for Laravel?
- For Laravel, use Quill directly via npm and Vite behind a Blade component, or evaluate Tiptap, TinyMCE, Lexical, or a Filament rich editor if you want maintained framework integrations. These give you control over the toolbar, asset pipeline, CSP behavior, and sanitization. The bundle itself is Symfony-specific, so there is no Laravel-native alternative within the package.
- Is nicolassing/quill-bundle actively maintained?
- No. The last release was 2021-01-22, the repository has roughly 9 stars and 0 dependents, and there is no evidence of CI or test coverage. That means no upstream security response and no compatibility work for newer Symfony, PHP, or Quill versions. Treat it as abandoned for planning purposes.
- Does nicolassing/quill-bundle work with Quill 2.x?
- Unclear, and likely not without changes. The bundle dates from 2021 and pins or assumes a Quill version from that era, while Quill 2.x changed APIs and sanitization behavior. Check the bundled asset version and test editor initialization, toolbar config, and HTML output before relying on it.
- How do I configure the Quill toolbar and editor options with this bundle?
- The bundle advertises configurable editor options and toolbar setup, typically through bundle configuration and the Twig or template helper that initializes Quill. In a Symfony app, inspect the bundle config and override the template if needed. In Laravel, skip the bundle and pass the Quill toolbar and modules configuration directly in your JavaScript or Blade component.
- What PHP and Symfony versions does nicolassing/quill-bundle require?
- The declared constraints live in the 2021-era composer.json, so expect older PHP 7.x and Symfony 4/5-era requirements unless the repository shows later updates. It is not verified against Symfony 6 or 7. Run composer why-not or inspect the require block before adding it to a modern Symfony application.