- How do I install lilac-wysiwyg/lilac in a Laravel app?
- Install it with Composer using composer require lilac-wysiwyg/lilac, then wire the editor into your Blade view. The release notes indicate a UMD bundle exposing window.Lilac, so you can often load dist/lilac.umd.js with a script tag and initialize the editor without a build step. There is no clear evidence of a Laravel service provider or publishable config, so expect to publish or copy assets manually and handle persistence yourself.
- Is lilac-wysiwyg/lilac a full Laravel package with a service provider?
- Based on the available release details, it does not look like a full Laravel package. There is no evidence of a service provider, config publish command, migration, or extra.laravel block. Treat the Composer package as a thin asset wrapper around the browser editor and plan to implement persistence, validation, sanitization, uploads, and rendering in your application.
- Does Lilac support image uploads in Laravel?
- Lilac advertises image upload support on the editor side, but it does not appear to ship a Laravel upload controller or storage integration. You will need an authenticated endpoint that validates file type with MIME sniffing, enforces size limits, stores the image, and returns a safe URL to the editor. Do not trust client-provided MIME types or filenames.
- How do I use Lilac with Livewire 3?
- Wrap the editor container with wire:ignore so Livewire does not morph the editor DOM. Listen for editor changes and sync content explicitly with $wire.set() rather than relying on default model binding. Use Alpine or small JavaScript glue for toolbar state and initialization, and test carefully after Livewire navigation events.
- What Laravel versions does Lilac support?
- The provided context does not specify Laravel or PHP version constraints. Because the PHP-side integration appears to be yours, compatibility mainly depends on your own routes, validation, storage, and rendering code. Test it in your target Laravel version and treat the current 0.7.x line as pre-1.0.
- Is Lilac safe for user-generated content and XSS?
- There is no documented security policy or explicit sanitization stance in the provided details, so stored XSS via paste or import remains a real risk. Sanitize all editor output server-side using a library such as mews/purifier or HTMLPurifier with a strict tag and attribute allowlist. Keep one canonical render path and never output raw editor HTML without filtering.
- Why is dist/lilac.umd.js missing in some Lilac versions?
- Version 0.7.1 appears to be a patch release whose purpose was to restore a missing dist/lilac.umd.js artifact. That suggests the publish pipeline shipped an incomplete tarball in 0.7.0 and did not smoke-test packed output. Inspect the actual Composer tarball you install, and redo any prototype built against 0.7.0.
- Does Lilac bundle the Qwik runtime, and how large is the payload?
- The release notes mention a Qwik-based playground, but they do not clarify whether Qwik is bundled in the editor artifact or required as a peer dependency. A bundled runtime increases the gzipped payload, while a peer dependency can create version conflicts in the host app. Check the packed UMD bundle and measure the gzipped size before production adoption.
- What format does Lilac persist, and can I round-trip it?
- Lilac is described as producing clean HTML output, but the canonical persisted format is not clearly documented. Decide whether you will store sanitized HTML, Markdown, or a JSON document tree, and verify that content can round-trip without data loss. For most Laravel apps, storing sanitized HTML or a JSON tree with a strict renderer is safer than trusting raw HTML.
- Is Lilac production-ready and actively maintained?
- Lilac is still pre-1.0 at 0.7.x, with a single maintainer and an unexplained release-date anomaly noted in the assessment. Treat minor upgrades such as 0.7 to 0.8 as migration events, verify every published artifact, and check commit cadence before locking the dependency. MIT licensing is clean, but review bundled third-party code and confirm accessibility and security expectations for your use case.