- Does philperusse/nova-tooltip-field support Laravel Nova 4 or Nova 5?
- Almost certainly not out of the box. The package was first and last released on 2018-11-14, which places it in the Nova 1.x era, and Nova's custom field API has broken at every major release since. Its Composer constraints were never updated for modern Laravel, PHP, or Nova versions, so expect to fork and port it rather than install it as-is.
- How do I install philperusse/nova-tooltip-field?
- The nominal install is a composer require followed by adding the field to a resource's fields() method. In practice you will first need to resolve Composer constraints against your current Laravel, PHP, and Nova stack. If the shipped asset is a prebuilt 2018 JavaScript bundle with no recoverable build step, installation turns into forking and rebuilding the front end or reimplementing the behavior.
- Is philperusse/nova-tooltip-field still maintained?
- No. It has a single release from November 2018, around 10 GitHub stars, zero dependents, and no maintenance activity in more than six years. There is no upstream maintainer to escalate issues to. The code is small enough to read and vendor if needed, but there is no supported upgrade path.
- What is the difference between nova-tooltip-field and Laravel Nova's built-in Field::help()?
- Nova's native Field::help() already provides contextual help text on fields without an extra dependency. The nova-tooltip-field package predates that capability and adds a hover info icon with tooltip copy beside a form input or detail value. Before adopting it, confirm whether native help text already satisfies your requirement, since that is the cheapest resolution.
- Does nova-tooltip-field work with keyboard navigation and screen readers?
- It is a hover-only affordance, which typically fails keyboard and screen-reader users and degrades on touch devices such as tablets. Where internal admin tools carry accessibility obligations, treat this as a compliance question rather than cosmetic polish. You would likely need to reimplement the component with focusable triggers and ARIA attributes.
- Can nova-tooltip-field show different tooltip text per record or per user?
- The package is described as static contextual guidance on fields, and there is no server-side data handling in the field. Whether tooltip copy can vary per record or user would require reading the Vue component source to confirm. If you need conditional or dynamic text, verify this before committing, because it changes the fork-versus-rewrite decision.
- Why does nova-tooltip-field break or render blank after a Laravel Nova upgrade?
- Nova custom fields are consistently among the first things to break at each major release, and this field was authored against the Nova 1.x generation. Failures are more likely to appear as a blank or unstyled field than as a thrown exception. That means the problem is often discovered by an operator misconfiguring a record rather than by a deploy, so plan a manual regression check after every Nova upgrade.
- Is the Vue source included in nova-tooltip-field, or only a compiled bundle?
- The evaluation indicates the package ships a prebuilt 2018 JavaScript bundle with no recoverable build step. That means you cannot easily audit or modify the front end without reconstructing the build tooling yourself. Confirm whether Vue source files are present in the repository before deciding to fork.
- What are the best alternatives to nova-tooltip-field for tooltip help in Laravel Nova?
- Start with Nova's native Field::help(), which covers most static help-text needs with zero extra dependencies. If you need richer content such as formatted text, links, or per-record conditional tooltips, build a small custom Nova field against your current Nova major using Vue 3 and Tailwind. That gives you a maintained, auditable component instead of a six-year-old bundle.
- Is nova-tooltip-field safe to install in a production Laravel Nova admin panel?
- There is no server-side data handling, no persistence, no HTTP surface, and no migrations, so the blast radius is confined to an authenticated admin surface. The concern is asset trust: a compiled JavaScript blob of unknown provenance would need source review and a rebuild before you can verify it. Treat it as a supply-chain review cost rather than a live exploit risk.