Nova Dependency Container Laravel Package

Product Decisions This Supports

• Build vs. buy for internal admin tooling: Nova Dependency Container provides conditional field logic (show/hide/require fields based on other field values) inside Laravel Nova, replacing bespoke Vue components or custom field classes. For a PM, this is a direct build-vs-buy decision: adopting the package saves days of implementation and ongoing maintenance for a common back-office form pattern.
• Roadmap for internal operations tools: Supports faster iteration on admin panels used by support, ops, finance, and compliance teams—for example, showing a refund reason only when an order status is "Refunded," or revealing compliance fields only for regulated customers.
• Use cases: Order management, customer onboarding, approval workflows, and any Nova resource where field relevance depends on prior selections. Reduces form clutter and data-entry errors without custom front-end work.
• Upgrade decision: v1.0.16 is a low-risk patch release. It removes debug logging, adds PHP 8.3–8.5 compatibility, improves behavior when Nova is absent, and passes tests/PHPStan. This supports a "safe to adopt/upgrade" recommendation, subject to standard dependency pinning.
• Vendor maintenance signal: The release demonstrates active maintenance (CI hygiene, static analysis, compatibility updates), which is a positive input when deciding whether to depend on a small open-source package for internal tooling.

When to Consider This Package

Consider adoption when:

• Your product or internal platform uses Laravel Nova for back-office or admin interfaces.
• Forms require conditional field behavior (visibility, required-if, dependent dropdowns) that would otherwise need custom Vue/Nova field development.
• Your team wants to reduce custom admin code and standardize how dependency logic is implemented across Nova resources.
• You are planning or running PHP 8.3, 8.4, or 8.5 upgrades; this release explicitly validates those versions.
• You want a production-ready patch with debug logging removed and clean static analysis before shipping admin tooling.

Look elsewhere when:

• You are not using Laravel Nova; the package is only useful within that ecosystem, and Nova itself is a separate commercial dependency.
• You need conditional logic in public-facing applications, multi-step wizards outside Nova, or non-Nova admin frameworks.
• You require an enterprise SLA, vendor support contract, or guaranteed long-term maintenance; this is a small open-source package and should be pinned and monitored.
• Your PHP version or Nova version falls outside the supported matrix; verify the minimum requirements before committing.
• You need highly custom field types or complex client-side reactivity beyond Nova's field system, where bespoke development may still be warranted.

How to Pitch It (Stakeholders)

Executive summary: Nova Dependency Container is a small open-source add-on for Laravel Nova that lets admin forms show or hide fields based on other field values. It removes a recurring piece of custom development work in back-office tooling. Release v1.0.16 is a production-readiness cleanup: debug logging removed, PHP 8.3–8.5 compatibility added, safer behavior when Nova is not installed, and clean tests/static analysis. It is a low-risk, non-breaking patch suitable for adoption or upgrade.

For engineering: v1.0.16 is a maintenance release with no reported breaking changes. It adds a class_exists check before registering Nova assets, fixes PHPStan errors and test failures in non-Nova environments, updates dependencies (collision ^8.6, pest ^3.7.4), and reduces the JS bundle from ~27.2KB to ~24.7KB. Recommend pinning the version and validating against your Nova and PHP matrix.

For product/operations: This package accelerates delivery of internal admin workflows—conditional fields, cleaner forms, fewer data-entry mistakes—without adding custom front-end maintenance. The main risk is reliance on a small open-source dependency; mitigate with version pinning and periodic review. Nova licensing remains a separate commercial consideration.