- How do I install awcodes/scribble in a Laravel Filament application?
- Install it with Composer using the exact pinned tag, for example composer require awcodes/scribble:0.8.1-alpha, because the package is archived and no later patch will float in through a caret range. Publish any config or asset files the package ships, then add the Scribble field to the form schema on your Filament resource or page. Confirm the asset publishing and panel registration steps against the repository README for the specific tag you install.
- Does Scribble support Filament v4 and current Laravel versions?
- The last release was 2024-09-26 and is tagged 0.8.1-alpha, with no Filament v4 tracking noted. Composer resolution against your Laravel, Filament, and PHP versions is the first thing to test before committing. If it does not resolve or boot cleanly on your stack, treat that as a stop signal rather than something to patch around.
- Is awcodes/scribble still maintained?
- No. The repository is archived, the latest tag is an alpha from September 2024, and there are zero dependents, meaning no downstream community is likely to inherit or patch it. There is no upstream pipeline for bug fixes or security bypasses. Plan for it as a vendored dependency with a named internal owner, or avoid it.
- What does Scribble give me that Filament's native RichEditor does not?
- Scribble is described as a lighter Tiptap-powered field with a focused toolbar, while Filament's native RichEditor is maintained in lockstep with the framework. If you cannot state the specific gap in one sentence, the correct choice is the native field. Document the justification before adopting an archived alternative.
- Does Scribble store HTML or Tiptap/ProseMirror JSON in form state?
- This is the exit-cost decision and should be verified in the source and on dehydrate before you adopt the field. The recommended approach is to persist plain HTML so a future field swap is a class change rather than a content migration. Wrap the field in your own factory class so replacing it later touches one file instead of every resource.
- How should I sanitize content saved through Scribble?
- Treat server-side sanitization as mandatory, not optional: clean markup on write and again on render, for example with mews/purifier or an equivalent. Rich-text fields persist markup that is often rendered unescaped, and with no upstream maintenance there is no bypass-fix pipeline. Backfill any legacy rows written before the sanitizer was in place.
- Is Scribble safe to use in production?
- It can be acceptable only with explicit controls: a pinned exact tag, an internal owner, a scheduled review date, and hardened sanitization on write and render. The lifecycle risk is high because the package is archived and alpha-tagged, and the security risk is effectively yours to manage. Without those controls, an archived rich-text dependency is a finding, not a shortcut.
- Can I customize Scribble's toolbar, theme, or appearance?
- The package is described as light and dark theme friendly and easy to customize, typically through published views, config, or assets. Because the front end is a compiled JS asset, deeper toolbar changes may mean editing published files or rebuilding assets yourself. Any customization increases your maintenance burden since there are no upstream updates.
- Can I use Scribble outside Filament, for example in a plain Livewire component?
- Scribble is built as a Filament form field that mounts a client-side editor into a Livewire-rendered form schema, so it is intended for Filament resources and pages. Using it outside that context is not the documented use case and would require extra wiring. For general-purpose Tiptap use, integrate Tiptap directly instead.
- What should I verify before adding Scribble to a project?
- First confirm what src, composer.json, and resources actually implement, because public descriptions of the package conflict and may describe different products. Then pin the exact tag, decide whether the field persists HTML, wrap the field in your own factory class, and name an owner with a review date. If the package turns out to include an AI text service, add a privacy and data-processing review before any text leaves your infrastructure.