- How do I install datomatic/nova-charcounted-fields?
- Install it with Composer via composer require datomatic/nova-charcounted-fields. It is a standard Laravel package, so service-provider registration follows normal Laravel conventions and the fields are then available inside your Nova resource classes. No bespoke infrastructure or data-store changes are implied by the package.
- Does this package support Laravel Nova 4?
- Version 2.0.0 is the release that added Nova 4 compatibility, so use that line if your application runs Nova 4. Nova 4 also raises the underlying Laravel and PHP baseline, so confirm your application satisfies those floors before upgrading. Always check the composer.json constraints of the exact tag you install.
- Will version 2.0.0 break my app if I am still on Nova 3?
- That is the key risk to verify. The 2.0.0 release is a major version bump but the changelog only mentions Nova 4 compatibility, which strongly suggests Nova 3 support was dropped from the Composer constraints. Inspect the diff or the composer.json of the tag before upgrading, and pin the latest 1.x release if you remain on Nova 3.
- How do I add a live character counter to a Nova text field?
- Replace the usual Text or Textarea field in your resource's fields method with the package's character-counted field classes. The counter updates live as the operator types in the Nova form. Configuration such as the maximum length is passed through the field's fluent options.
- Can I enforce a maximum length on a Nova textarea?
- Yes. The package supports optional maxlength enforcement in addition to the visible counter, so submissions that exceed the configured limit are rejected rather than merely flagged. Enforcement is optional, so you can also use the counter purely as guidance. Limits are configurable per field, so different resources can carry different rules.
- Do I need to publish or rebuild assets after installing?
- Normally the compiled front-end assets ship with the package and no publishing step is required. However, Nova 4 moved to a Vue 3-based tooling stack, which commonly breaks custom-built fields that were compiled against older Nova versions. If you are upgrading from Nova 3, confirm the release you install actually regenerated its compiled assets against the Nova 4 toolchain.
- Is this package a risk to my production application?
- Blast radius is narrow because the package only extends Laravel Nova, the admin layer, and is not on the core request path. The main concerns are version-matrix conflicts and the fact that a one-line changelog for a major release gives little evidence of what was tested. Treat it as a leaf dependency in the admin UI and verify the diff before adopting a major bump.
- Is datomatic/nova-charcounted-fields actively maintained?
- The available signal is thin: the release note content is a single line about Nova 4 compatibility, which is a maintenance-style release rather than a feature expansion. Before committing, check commit recency, open-issue count, and how quickly prior Nova majors were supported. Confidence in any assessment here is low without inspecting repository activity directly.
- What are the alternatives to this package for character limits in Nova?
- You can use Nova's built-in field options and validation rules to cap length without any extra dependency, though you lose the live counter in the form UI. Writing a small custom Nova field is the other common route, at the cost of maintaining the compiled assets yourself. This package is worth adopting mainly if you already run Nova and want the counter behaviour without building it.
- Does this package expose models, events, or config used outside Nova?
- Based on the package description, it is a Nova field extension only, with no indication of models, events, or configuration consumed by application code. That means a break would surface in the admin UI rather than in your domain logic. Verify this yourself if you depend on any behaviour beyond rendering, since the changelog does not document the public surface.