Nova Input Group Laravel Package

Product Decisions This Supports

• Form UX polish on internal admin surfaces. This package turns a Nova 4 text field into a prefix/suffix "input group" (e.g., currency symbols, unit labels, URLs, percentages). The product decision it unlocks is whether to spend design/engineering cycles on admin-panel ergonomics at all — this lets you ship that polish for the cost of a composer require rather than a custom Nova field build.
• Build vs. buy for Nova custom fields. A custom Nova field is typically a few hours to a day of engineering plus ongoing maintenance across Nova upgrades. At 3 stars and 0 dependents, this package is cheap to adopt and cheap to abandon — the build-vs-buy math favors "buy (copy)" for anything that isn't core to your product's differentiation.
• Consistency across admin data entry. Prefix/suffix grouping reduces mis-entry on money, percentage, and unit fields — a real (if modest) data-quality lever for ops teams keying in pricing, discounts, or thresholds.
• Scope control on internal tooling roadmaps. You can defer a broader "internal design system for Nova" initiative and satisfy immediate stakeholder requests (e.g., "the price field should show a $ sign") with a narrow, low-blast-radius dependency.
• Not a customer-facing decision. This does not affect end-user experience, performance, or architecture. It should be classified as internal tooling, not product surface — which means it should not consume roadmap priority slots.

When to Consider This Package

Consider it when all of the following hold:

• You are on Laravel Nova 4 specifically. Nova 5+ compatibility is unverified — check the repo's commit recency and composer.json constraints before assuming it works on an upgrade.
• You need only text fields with visual adornments (prefix/suffix labels). If you need masked input, numeric formatting, or validation logic tied to the adornment, this isn't the tool.
• Your team is comfortable vendoring or forking a small package. With 3 stars and 0 dependents, treat this as "a snippet with a Composer wrapper," not a maintained library. Plan to own it.

Look elsewhere (or write it yourself) when:

• You're not on Nova. This is Nova-only and has zero value outside it. If you're on Filament, Blade + Tailwind, or Vue admin tooling, close the tab.
• You need long-term maintenance guarantees. No dependents and a low star count means no community safety net. If your org has a policy against low-traction dependencies, this fails it — but note that a Nova field is a self-contained Vue component; forking it into your own nova-components/ directory is a ~1 hour task and removes the dependency risk entirely.
• You need more than cosmetics. Required/optional adornments, validation feedback styling, or multi-language label handling aren't in scope.
• Procurement/security review is heavy. The cost of reviewing a 3-star dependency may exceed the cost of reimplementing the component internally. In that case, reimplement.

How to Pitch It (Stakeholders)

For executives: This is a small, free (MIT) UI helper that makes internal admin forms clearer — for example, showing a "$" prefix on price fields so ops staff don't mis-key values. It's zero-cost, low-risk, and touches only the internal Nova admin panel, not the customer-facing product. It is not a strategic investment and should be framed as a tactical dev-experience improvement.

For engineering: It's a Nova 4 text field rendered as an input group. Adopt it if you want the affordance in under an hour; otherwise the underlying Vue component is trivial to fork into nova-components/ and own outright. Recommendation: fork it rather than depend on it — with 3 stars and 0 dependents, the supply-chain and maintenance risk is low but nonzero, and a fork costs almost nothing. Verify Nova 4 compatibility and license attribution (MIT, retain the notice) before merging.