- How do I install noin/filament-forms-tinyeditor in a Laravel Filament app?
- Install it with composer require noin/filament-forms-tinyeditor, then confirm whether service provider auto-discovery is enabled or register the provider manually. You can optionally publish config or views if the package documents those assets. After installation, add TinyEditor::make('content') to a Filament form schema. Check the composer constraints against your pinned Filament version before running composer update.
- Which Filament and Laravel versions does this TinyEditor field support?
- The integration context expects Laravel with Filament v3 or v4, Livewire 3, and PHP 8.1 or newer, but you should confirm the exact composer constraints. Filament field APIs have changed between majors, so an unpinned or loosely pinned dependency can block composer update in a monorepo. Verify compatibility against your pinned Filament version before planning production use.
- Does this package work with Livewire re-renders, repeaters, and modal forms, and how should I test it?
- That is the main technical risk area: TinyMCE owns the DOM node and mutates it outside Alpine and Livewire reactivity, so correctness depends on explicit change and blur event wiring plus wire:ignore on the wrapper. Editors inside repeaters, modals, and nested relation forms are classic breakage cases and should be assumed broken until proven otherwise. Test re-hydration after Livewire re-renders and confirm $wire.set calls fire correctly. Treat those scenarios as required test cases before rollout.
- Do I need a TinyMCE API key or Cloud account to use this editor?
- It depends on whether the package loads TinyMCE from a CDN or vendors it locally. TinyMCE 6+ core is MIT licensed, but Cloud delivery, premium plugins, and many trial bundles are commercially licensed and gate on an API key. Inspect the package source and config before production, because a CDN dependency can expose keys in client markup and affect CSP. This is a procurement question as well as a technical one.
- Is content from this TinyMCE field safe from stored XSS?
- No. Rich text is a stored-XSS surface, and client-side editor filtering is not a security control. Add server-side sanitization with an allowlist, such as HTML Purifier or an equivalent library, regardless of package behavior. If the package or its config exposes image or file upload endpoints, add authorization, MIME sniffing, and size limits.
- How do I configure TinyMCE toolbars and plugins in the Filament form field?
- The package overview says toolbars, plugins, and editor options can be configured directly when adding the field to a Filament schema. In practice, check the README and source for the supported method names or config array, and publish any config file if provided. Keep the toolbar configuration small at first, then add plugins only after confirming their licensing and loading method.
- Can I use this TinyEditor field alongside Filament's built-in RichEditor?
- Yes, the two can coexist per resource, which is useful for a staged rollout. Storage semantics match Filament's native RichEditor because both store an HTML string in a text or longText column, so the data model does not change. You can migrate forms gradually without rewriting existing content fields.
- Who maintains noin/filament-forms-tinyeditor and is it safe for production?
- The available assessment flags supply-chain and governance risk: zero stars, zero dependents, a single maintainer, and a namespace mismatch between the noin/ Packagist vendor and the Tinnnooo repository owner. That pattern is common in typosquatting or handoff scenarios, so verify Packagist ownership, commit history continuity, and vendor transfers. Treat it as unvetted third-party code and read the source before it touches production. The package is MIT licensed.
- How should I handle image or file uploads with this TinyMCE editor?
- The assessment found no documented sanitization or upload story, so assume upload handling is entirely your responsibility. Any endpoint exposed by the package or its configuration needs authorization checks, MIME sniffing, size limits, and safe storage paths. Do not rely on the editor's client-side filters to reject unsafe files or markup.
- What are the alternatives if this package is abandoned or incompatible?
- Filament's first-party RichEditor is the obvious alternative and shares the same HTML string storage model. If you need TinyMCE specifically, check whether the field class and Blade view are small enough to vendor and maintain internally. Given the low adoption and uncertain release cadence, have a fallback plan before making it part of a critical admin workflow.