- Which Laravel Nova versions does nurmuhammet/dynamic-fields support?
- This is a Nova field extension, so its compatibility is pinned to whichever Nova major the bundled Vue component was compiled against. Nova 4 (Vue 2/Inertia) and Nova 5 (Vue 3) have incompatible asset pipelines, and a compiled asset almost certainly targets only one of them. Check composer.json constraints for laravel/nova, php, and illuminate/*, then test against the exact minor version you run in production. Treat any unpinned nova constraint as a red flag.
- How do I install nurmuhammet/dynamic-fields in a Laravel app?
- Require the package with Composer, optionally publish its assets, and register the field class in the fields() method of the Nova resource where you need it. Then rebuild Nova assets so the compiled Vue component is picked up. The integration surface is small and conventional, so a competent Laravel developer should complete a working spike in under a day.
- What does dynamic fields actually mean in this package?
- The package lets you define field types and configurations, then let users create and manage their own custom fields and values without schema changes. In a Nova context that typically means user-defined field sets and conditional field behavior rendered across create, update, and detail views. Before adopting it, confirm whether your requirement is conditional visibility, conditional options, dependency-driven value mutation, or server-side computed fields, because each maps to different implementation work.
- Is the dynamic behavior enforced server-side or only in the Vue component?
- Nova field visibility logic is usually presentation-layer only, so if it lives in the compiled Vue component, hidden inputs can still be submitted. Enforce validation and authorization independently in your FormRequest rules() and in the Nova resource authorize() methods. Do not rely on the field's conditional display as a security or data-integrity control.
- Can I replace this package with Nova's native dependsOn helpers?
- Nova ships dependsOn, hideWhenCreating/showWhenCreating, and other conditional visibility helpers that cover a meaningful share of dynamic field use cases. Before adding a dependency with little community signal, try reproducing your hardest form requirement natively plus a small custom field. If native helpers meet the requirement, dropping the third-party package is the lower-risk choice.
- Does this package work with Filament, Livewire, or plain Blade admin panels?
- No. It extends Laravel\Nova\Fields\Field and ships a compiled Vue component registered through NovaServiceProvider::fields(), so it only has value if Nova is already your admin layer. That means a paid Nova license and a Nova-compatible Vue toolchain are prerequisites. If your admin stack is Filament, Livewire, or hand-rolled Blade, close this out immediately rather than re-evaluating it later.
- Is nurmuhammet/dynamic-fields production-ready and actively maintained?
- The repository has roughly two stars and zero dependents, which means effectively no production signal and no downstream pressure to fix breakage. It is a single-maintainer Nova field package, a category that is structurally fragile because Nova majors change the field and Vue contract. Check for recent commits, tagged releases, CI configuration, and unanswered issues before you commit to it.
- What license does nurmuhammet/dynamic-fields use?
- Licensing is not surfaced in the repository listing, and the absence of a LICENSE file is a procurement blocker regardless of code quality. Confirm that a LICENSE file exists and that it is permissive enough for your organization before starting the spike. Resolve license ambiguity first, not after you have built a form around the field.
- Do I need to publish assets and rebuild Nova's frontend to use this field?
- Yes. Nova field packages ship a compiled Vue component, so you will run the vendor publish step and rebuild Nova assets, typically via nova:publish. Confirm whether the build targets Vite or Mix and whether it matches your Nova install, since Nova 4 and Nova 5 differ here. If the asset pipeline mismatches, the field may not render at all.
- How should I test a Nova dynamic field before adopting it in production?
- Run a two-to-three day time-boxed spike in a sandbox: install it, register the field on one resource, reproduce your hardest form requirement, and confirm how server-side validation behaves. Test across create, update, and detail views, plus inline relationship and ActionModal contexts, because dynamic behavior is easy to demo but hard to get right everywhere. Adoption is a code-level addition with no data model or persisted state, so switching cost in and out is low, which supports a pilot rather than a formal commitment.