- How do I install johnathan/nova-trumbowyg in a Laravel Nova application?
- Install it with Composer using the package name johnathan/nova-trumbowyg, then register the field class in the relevant Nova resource. Publish the package assets if the README requires it, and confirm the editor loads in a staging Nova form. Because the package is a thin Nova field wrapper, most setup is standard Nova field registration rather than general Laravel configuration.
- Which Laravel, PHP, and Nova versions does nova-trumbowyg support?
- The last release was 2019-09-19 and it targets the Nova 2.x era, likely with PHP 7.x and older Laravel constraints. There is no evidence of support for Nova 4, Nova 5, or modern PHP and Laravel releases. Validate the Composer constraints against your exact Nova, Laravel, and PHP matrix before committing.
- Is johnathan/nova-trumbowyg still maintained?
- No. The package appears unmaintained, has a small user base, and its GitHub releases and issues are stale. Expect to pin, fork, or patch it internally, and do not rely on an upstream SLA for production support.
- How do I configure the Trumbowyg toolbar options in Nova?
- The field wraps Trumbowyg and exposes toolbar and options configuration through the Nova field definition. Pass the supported options array in your resource and check the README for exact key names and accepted values. Keep the configuration minimal and test the rendered toolbar after any Nova or asset pipeline change.
- Is the HTML saved by nova-trumbowyg sanitized to prevent XSS?
- The package is an editor UI wrapper; the provided context gives no evidence that it sanitizes HTML server-side on save or render. Treat all editor output, including pasted and source-mode HTML, as untrusted and sanitize it in your application before storage or display. Also constrain uploads and allowed tags according to your security policy.
- Can I use nova-trumbowyg with Laravel Nova 4 or Nova 5?
- There is no evidence that johnathan/nova-trumbowyg works with Nova 4 or Nova 5. Its 2019 release predates those versions, so field registration, asset publishing, and frontend behavior may break. For modern Nova, treat this as a replacement project and evaluate a maintained editor field or an internal wrapper.
- What are the best maintained alternatives to nova-trumbowyg for rich text in Laravel Nova?
- Look for actively maintained Laravel Nova rich-text or WYSIWYG fields, or build a small internal Nova field around a current editor such as TipTap, Quill, or a maintained Trumbowyg fork. Compare Nova version support, sanitization options, upload handling, accessibility, and release cadence. Do not assume upgrading this package is cheaper than replacing it.
- Does nova-trumbowyg work for public-facing Laravel forms or only Nova admin?
- No. It is a Laravel Nova custom field, not a general Laravel form component or standalone editor integration. Use it only inside a Nova admin panel on a verified compatible Nova version, not for public-facing forms or non-Nova Laravel apps.
- How should I test nova-trumbowyg before using it in production?
- Run a time-boxed spike in staging: pin the package version, install it, publish assets, and register the field on one non-critical Nova resource. Test create, edit, render, paste, source-mode, and sanitization flows, and verify the editor loads under your current Nova frontend. Define rollback and content-migration steps before expanding to production fields.
- What are the production risks of using an unmaintained Nova WYSIWYG field?
- Key risks include Nova upgrades breaking field registration or assets, Composer conflicts, stale JavaScript dependencies, and XSS from unsanitized HTML. Upstream fixes are unlikely, so you must budget for fork ownership, security review, and Nova upgrade testing. Runtime load is low because the editor appears only in admin forms, but content sanitization and browser performance on large HTML payloads still matter.