Weave Code
Nova Tags Field Laravel Package
palauaandsons/nova-tags-field
A Laravel Nova field for adding tag-style input to your resources. Lets editors attach multiple tags through a clean, searchable interface, making it easy to organize, filter, and manage records from the Nova admin panel.
A tags field for Nova apps that uses cartalyst/tags
Frequently asked questions about Nova Tags Field
- How do I install palauaandsons/nova-tags-field in a Laravel Nova app?
- Install it with Composer using composer require palauaandsons/nova-tags-field, then add the package's field class to the fields() method of the Nova resources that need tagging. After registering the field, run php artisan nova:assets so Nova picks up the compiled assets. The install is mechanically trivial, but confirm your app has an active Nova license first, since the package has no value outside Nova.
- Does this package support Nova 5 and current Laravel versions?
- Nova 5 compatibility is unverified. The last release was 2023-03-31, and the only recent upkeep signal is a cosmetic dark-mode CSS PR, which suggests the package is a Nova 4-era artifact. Test it in a staging app against your exact Nova and Laravel versions before committing to it, and treat Nova 5 support as something you may have to add yourself.
- Does nova-tags-field use cartalyst/tags or store tags as a JSON column?
- The documentation is contradictory: the description says it uses cartalyst/tags, while the integration guidance describes persisting a flat JSON array with an array/AsArray cast. Those are materially different data models. cartalyst/tags implies a polymorphic taggable pivot, a shared tag namespace, and migrations you own, whereas a JSON column means per-record arrays and whereJsonContains filtering. Read the shipped 4.0.1 source and migrations before deciding your schema.
- Is palauaandsons/nova-tags-field still maintained?
- Treat it as best-effort rather than actively maintained. It has roughly 10 stars and zero dependents, so there is no evidence of production use, and releases stopped in early 2023 apart from a cosmetic 4.0.1 patch. There is no SLA or visible issue-response commitment, which at this adoption level means you are effectively buying a fork with a head start. Budget for vendoring the field if upstream goes dark.
- How do I add the tags field to a Nova resource?
- Add a single field entry to the resource's fields() method, pointing at the package's tags field class, then rebuild Nova assets. No routing, service providers, or domain code changes are required, which is why the blast radius is limited to a few admin screens. Keep the field usage in one place so you can swap it for a plain text input if needed.
- Can I filter Nova resources by tags with this field?
- Filtering depends entirely on which storage model the shipped code actually uses. If it integrates cartalyst/tags, you get a shared tag namespace and cross-model queryability through the polymorphic pivot. If it stores a JSON array on the model, filtering relies on whereJsonContains, which will not scale well to large datasets. Confirm the data model before you design any tag-based index or lens.
- What are the alternatives to this Nova tags field?
- Alternatives include using cartalyst/tags directly with a custom Nova field, Nova's built-in relationship fields backed by a tags table, or a maintained third-party Nova tag field. For low-stakes labelling, a comma-separated Nova Text field is a few hours of work and has no dependency risk. Choose based on whether you need a reusable shared taxonomy or just per-record labels.
- Is this package safe to use in production?
- Adopter risk is low because the package is MIT licensed, small, confined to the admin UI, and easy to remove. The bigger concern is that a tag control renders user-supplied text in chips and dropdowns, and there is no documented security review or escaping audit. Verify output escaping in the shipped code yourself, and restrict who can edit tags in production.
- Does nova-tags-field have tests or CI?
- There is no documented test coverage, CI pipeline, or support expectation in the package's signals. With zero dependents there is also no proxy evidence of battle testing across real applications. Write your own smoke test around the field's save and load behavior, especially if you rely on tag filtering in Nova lenses or metrics. Treat upstream fixes as best-effort.
- Can I use nova-tags-field outside Laravel Nova?
- No. This is a Nova field package and has zero value in a plain Laravel app, since it plugs into a Nova resource's fields() method and renders an admin-only input. For non-Nova tagging, use cartalyst/tags directly or another general-purpose tagging package. Confirm Nova is licensed and actively used before spending any engineering time here.
Weaver
How can I help you explore Laravel packages today?