Weave Code
Nova Toast Ui Editor Field Laravel Package
bbs-lab/nova-toast-ui-editor-field
A Laravel Nova field that brings the Toast UI Editor into your admin panel, giving users a rich markdown and WYSIWYG editing experience with live preview, so long-form content is easier to write and manage.
Toast UI Editor field for Laravel Nova.
Frequently asked questions about Nova Toast Ui Editor Field
- How do I install bbs-lab/nova-toast-ui-editor-field in Laravel Nova?
- Install it with composer require bbs-lab/nova-toast-ui-editor-field, then declare the field on the Nova resources that need rich text authoring. There are no migrations, config files, or queue implications, but you do need a valid Nova license and a Nova major the package supports. Depending on how the service provider registers assets, you may also need to publish or serve the compiled JS.
- Does this field store Markdown or HTML in the database?
- The Toast UI Editor supports both Markdown and WYSIWYG modes, but the release notes do not document which format the field persists. Check the field configuration and your column contents before swapping editors, because the stored format drives your render pipeline, sanitization policy, and search behavior. Never mix Markdown and HTML in the same column.
- Which Laravel and Nova versions does nova-toast-ui-editor-field support?
- Version 2.1.0 exists primarily to add Laravel 13 support, which is a classic version-catch-up release for a wrapper package. The release notes do not spell out whether constraints were widened or minimums raised, so read composer.json at the v2.1.0 tag for the exact PHP, Laravel, and Nova floors. A valid Nova license and a matching Nova major are required regardless.
- How do I add the Toast UI Editor field to a Nova resource?
- Add the package's field class to the fields method of your Nova resource, pointing it at the Eloquent attribute you want to edit, then ensure the compiled field assets are published or served. The blast radius is limited to the resources that opt in, so you can adopt it incrementally. Confirm the exact class namespace and asset steps against the README for your tagged version.
- Is the Toast UI Editor output sanitized against XSS?
- The package is a thin adapter around @toast-ui/editor and does not document server-side sanitization, so treat sanitization as your responsibility. Sanitize HTML output in the host application before rendering, or render stored Markdown through a safe parser with raw HTML disabled. Upstream TOAST UI Editor has a history of XSS and DOM-clobbering advisories, so pin and audit the bundled editor version.
- Can I replace a Textarea, Markdown, or Trix field with this editor?
- It is a drop-in for Nova attributes currently using Textarea or Markdown fields when both sides store Markdown in the same column. Replacing Trix or Text fields is riskier because those store HTML, so plan a content normalization step rather than mixing formats. The field is a poor fit if you need structured block content, collaborative editing, or authoring outside Nova.
- How are the field's JavaScript and CSS assets published and served in Nova?
- The package ships a compiled Vue/JS bundle registered with Nova's field registry, plus a PHP Field subclass for the server-side definition. Depending on the service provider, you either publish the assets or serve the compiled JS directly. After any Nova or package upgrade, re-publish assets and clear caches, since asset pipeline breakage is the dominant day-2 failure mode for custom Nova fields.
- Does this package work outside Laravel Nova?
- No. It is a Nova form field and provides no value outside a Nova admin panel. If you need the same editing experience in a standalone Laravel app or a non-Nova front end, use the upstream @toast-ui/editor bundle directly or a framework-agnostic wrapper instead.
- Is nova-toast-ui-editor-field actively maintained, and what are the alternatives?
- It is a single-author package with modest issue volume, no vendor SLA, and a low-cadence release pattern where framework compatibility arrives reactively after majors ship. Treat it as an internal dependency you may eventually need to fork, especially if you track Laravel or Nova releases closely. Alternatives include Nova's built-in Markdown and Trix fields or other editor wrappers if you do not specifically need TOAST UI.
- How do I upgrade from v2.0.0 to v2.1.0, and does it support Laravel 13?
- v2.1.0 is an additive compatibility release that adds Laravel 13 support, so it should be a low-risk minor for most consumers. Verify in composer.json that the widened constraint did not silently raise your minimum PHP or Nova version, and sequence the framework/Nova upgrade together with this bump, since the package alone delivers nothing until you are on the target stack. Afterwards, re-publish assets and clear caches as usual.
Weaver
How can I help you explore Laravel packages today?