- What is pekhota/nova-hugerte and what problem does it solve?
- It is a Laravel Nova custom field that wraps the HugeRTE rich text editor, a fork of TinyMCE, so Nova resources get a full WYSIWYG editing experience. It removes the need to hand-roll a custom Vue field or bolt a third-party editor into the Nova frontend yourself. It fits inside an existing Laravel and Nova admin panel with no extra service, database, or separate frontend stack.
- How do I install pekhota/nova-hugerte in a Laravel Nova application?
- Install it with Composer, then publish the package assets and configuration using the standard Laravel vendor publish command so the editor scripts are served from your public directory. Register the field class on the Nova resource you want to edit, typically inside the fields method, and pass any editor options you need. Finally, run your asset build and load the Nova admin panel to confirm the field renders and saves.
- Which Laravel and Nova versions does pekhota/nova-hugerte support?
- Version 1.2.0 is a compatibility release that widens support to Laravel v13, on top of the earlier Laravel and Nova range. Because Nova has its own release cadence, confirm that your specific Nova version also supports the Laravel release you are running rather than assuming the widened Composer constraint covers every combination. Check the package's composer.json and README for the exact tested matrix, and validate PHP and browser requirements in staging before committing to production.
- What changed in pekhota/nova-hugerte version 1.2.0?
- The 1.2.0 release is described as a compatibility release adding Laravel v13 support with no stated API or behavior changes. In practice that usually means widened Composer constraints rather than new runtime code, though the release notes should be checked for asset or configuration tweaks. Treat it as a signal to re-test the editor rather than as proof that every Nova and PHP combination works.
- How do I customize the toolbar and editor options in Nova?
- HugeRTE keeps a TinyMCE-compatible configuration surface, so toolbar layout, plugins, menubar, and content styling are passed through as editor options from the field definition or the published config. Set the options you need per field so different resources can have different editing experiences, and keep the configuration in version control. If you are migrating from an existing TinyMCE setup, move options across deliberately, since config parity is not guaranteed.
- Is Hugerte actively maintained, and how are editor security issues handled?
- Hugerte is a community fork of TinyMCE, so its maintenance depends on its own maintainers rather than on the upstream Mirusoft team. That means editor-level CVEs may take longer to be patched than in TinyMCE, and you should track both the fork's releases and the package's releases. As a practical mitigation, pin versions, subscribe to security advisories, and keep the option to swap the underlying editor or fork the field if upstream responsiveness slips.
- Does pekhota/nova-hugerte work with Content Security Policy and Vite asset builds?
- Editor assets are static files served through your Laravel application, so they work alongside Vite or Mix as long as the published files are actually accessible from the browser. A strict Content Security Policy can block the editor's scripts or inline styles, so test with your production CSP rather than only in local development. If your policy forbids unsafe-inline, expect to add nonces, hashes, or adjust the editor configuration accordingly.
- How do I handle image uploads with the HugeRTE field?
- The field gives you the editor integration; file handling is still your application's responsibility, so an image or file upload must be wired to your own endpoint or Nova storage disk. Configure the editor's upload options to point at a route you control, and enforce validation, size limits, and authorization there. Missing or misconfigured upload adapters are one of the most common failure modes, so smoke test uploads in staging before promoting.
- Can I use pekhota/nova-hugerte outside Nova, or migrate from an existing TinyMCE setup?
- No, it is a Nova custom field and depends on Nova's field lifecycle, so using it outside an admin panel would require additional glue code. If you are replacing an existing TinyMCE or Hugerte integration inside Nova, migrate editor configuration and content sanitization rules carefully rather than assuming they behave identically. Alternatives to consider are TinyMCE-based Nova packages, Nova's built-in text and markdown fields, or a bespoke Vue field if you need tight control.
- How should I test and upgrade pekhota/nova-hugerte safely in production?
- Upgrade Laravel and Nova first, then the package, then re-publish the assets, because the field is coupled to both Nova's custom-field API and Laravel's asset publishing conventions. After upgrading, run editor smoke tests covering formatting, links, image uploads, and sanitization, verify CSP behavior, and regression-test how existing stored content renders. Keeping a pinned previous version gives you a quick rollback if the editor breaks after a Nova release moves ahead of the package.