Weave Code
Filament Custom Tiptap Extensions Laravel Package
codedor/filament-custom-tiptap-extensions
Custom Tiptap extensions for Filament's RichEditor, giving Laravel and Filament apps extra rich-text formatting and editor capabilities. Integrate additional Tiptap tools into Filament forms with a simple, package-friendly setup.
Some custom extensions for Filament tiptap
Frequently asked questions about Filament Custom Tiptap Extensions
- What is codedor/filament-custom-tiptap-extensions used for?
- It is a Filament plugin that ships custom Tiptap extensions for Filament's RichEditor field, adding extra rich-text formatting and editor capabilities to Laravel admin panels. The value is concentrated in editor UX rather than domain logic, so it is a presentation-layer package. It fits wherever a Laravel and Filament app already exists and needs richer authoring than the stock TipTap setup.
- How do I install this package in a Laravel Filament app?
- It is Composer-installable with no infrastructure prerequisites. Typically you run composer require codedor/filament-custom-tiptap-extensions, register the plugin in your Filament panel provider, and publish or build the editor assets. Check the README for the exact registration call and asset publish tag for your Filament version. Because it is additive, there are no migrations and no service-provider bootstrapping that touches core app behaviour.
- Which Filament versions does this plugin support?
- The package tracks Filament's rich-text editor internals, which have moved between Filament 3 and Filament 4, so confirming your Filament major version is the single go/no-go check. Treat version alignment as the first thing you verify, ahead of anything else. If you are on the wrong major, the extension API may not match.
- Is it compatible with Laravel 13 and PHP 8.5?
- Release 2.2.0 added PHP 8.5 and Laravel 13 support, but that compatibility PR was authored by a bot. Before relying on it, read the diff and confirm the CI matrix actually exercises stable PHP 8.5 and Laravel 13 rather than pre-release or prefer-lowest-only combinations, because a green badge can mean installs, not works. Also verify your target versions are inside the tested matrix, not just the composer.json allow-list.
- Does this package require database migrations or config changes?
- No. It is additive: it registers Tiptap extensions for the editor and ships no migrations, queue jobs, or event hooks. Rollback is simply unregistering the plugin and republishing assets, with no data migration involved. That makes it low-risk to trial on a single admin surface.
- How do I add the extensions to a RichEditor field?
- Register the plugin, publish its assets, and attach the extensions to one RichEditor field. Start greenfield on a non-critical surface such as an internal CMS or marketing page editor rather than retrofitting an existing production editorial workflow. Verify what each extension does in the editor before rolling it out further.
- Do I need to build or publish front-end assets for the Tiptap extensions?
- Yes. The real integration effort sits in the front-end layer: asset build and publish, CSP compatibility for the editor bundle, and validating stored HTML against the new node schema. Check whether the plugin vendors or CDN-loads TipTap, since that determines whether it survives a strict CSP or air-gapped requirement. Publish assets in a branch first and confirm the editor loads cleanly before merging.
- Will existing stored HTML still render if I remove the plugin?
- Existing content remains in your database, but nodes that only the custom extensions understand may not render in the stock Filament editor. That exit cost is the main thing to assess before adopting. If the extension set is small, consider pinning to just the specific extensions you consume rather than adopting the plugin wholesale.
- How should I test this plugin before using it in production?
- Treat it as a spike, not a project. Pin the exact plugin version, verify PHP and Laravel constraints against your runtime, confirm the Filament major version match, then build and publish assets in a branch and exercise the editor on one non-critical admin surface. Check the rendered HTML and any CSP behaviour before promoting it.
- Is this package well maintained, and what are the risks?
- It looks like a single-maintainer, niche package with a small contributor pool, and the only new contributor in release 2.2.0 was a bot, so bus factor is the dominant long-term risk rather than code quality. Release 2.2.0 itself is a minor bump containing only CI dependency updates plus the compatibility PR, and those dependabot changes do not ship in the runtime artifact. Pin versions and review diffs on upgrade.
Weaver
How can I help you explore Laravel packages today?