- How do I install think.studio/nova-html-field in a Laravel Nova application?
- Install it with Composer using the package name think.studio/nova-html-field, then reference the field class inside your Nova resource's fields() method. There is no documented publish or config step, and the package is described as a drop-in field with zero dependencies. Before installing, confirm the package is actually published on Packagist with tagged releases and pin an exact version in composer.json rather than relying on a floating constraint.
- Which Laravel and Nova versions does nova-html-field support?
- Supported Nova, Laravel, PHP and Vue versions are not documented in the package description, and that is the first thing to verify. Nova custom fields are tightly coupled to the Nova major version and its Vue runtime, so a package that has not tracked recent Nova releases can break silently. Read the composer.json constraints and run a spike against a staging Nova install before committing to it in a production application.
- Does nova-html-field sanitize the HTML it renders?
- Sanitization behavior is not documented, so treat the field as a stored-XSS surface until you have read the source end to end. Because it renders raw HTML inside your admin panel, sanitize input server-side with a strict allowlist library before it is saved, rather than trusting anything downstream. Also limit who can edit resources that use the field, since Nova is a high-privilege surface.
- How do I add the HTML field to a Nova resource's fields() method?
- Add the package's field class to the resource's fields() array like any other Nova field, passing the attribute name that holds your HTML string. The exact class name and namespace should be taken from the package source or README rather than guessed. Keep the field definition isolated so it can be swapped for a different implementation with a one-line change later.
- Does nova-html-field work with Nova's hide and show visibility rules?
- Yes, the package is described as supporting Nova's visibility rules, including dependsOn, because it registers as a standard Nova field. That means you can conditionally show or hide the HTML block based on other field values in the same form. Confirm the behavior in a spike if your layout depends on rules firing on index or detail views, since only detail and form rendering are explicitly stated.
- Does nova-html-field render in both detail and form views?
- The package overview states it renders raw HTML in Nova detail and form views. Index and inline creation contexts are not called out, so verify those paths in the source or a staging spike if your resource needs them. For instructional callouts and formatted notices, detail and form coverage is usually enough.
- Is nova-html-field safe to use in production, and what license does it use?
- There is no production signal: no stars, no dependents, and a single maintainer, and the license metadata resolves to NOASSERTION rather than a recognized license. A raw HTML field is also a stored-XSS surface inside your most privileged admin area, and custom-field Vue components tend to break quietly on Nova upgrades. Get the license confirmed in writing, review the source, and consider forking and vendoring it with server-side sanitization if you do adopt it.
- What are the alternatives to nova-html-field for showing HTML content in Nova?
- Nova's built-in text and formatted-text fields cover most cases where you only need readable formatted content rather than arbitrary markup. If you need HTML authoring, compare against a maintained WYSIWYG field package, or write a small in-house Nova field, which is typically a service provider plus a Vue component. That in-house route is usually one to three days of work and removes the licensing and maintenance risk entirely.
- How do I test a Nova custom HTML field before shipping it?
- The package does not document tests or CI, so plan to write your own coverage. At minimum, assert the field appears in the resource's fields() output, assert the stored value round-trips through the model, and exercise the render path in a staging Nova install after each Nova upgrade. If compiled assets ship in the package, inspect them so you are not deploying opaque JavaScript.
- Does nova-html-field require a database migration or a specific column type?
- The package does not ship migrations; the field simply reads and writes whatever attribute you point it at, typically a text or longText column you already have. Keep that column generic and nullable so it survives swapping the field for a different implementation later. Adding the column is your migration, not the package's.