- How do I install drobee/nova-sluggable in Laravel Nova?
- Install it with Composer as a Nova field package, then add the field to the target Nova resource. Because Nova is a privately hosted paid package, CI and fresh environments must already have Nova repository credentials configured before composer install can succeed.
- Is drobee/nova-sluggable compatible with Laravel Nova 4 or Nova 5?
- The package targets Laravel Nova, but the provided context does not state a verified Nova major. The evaluation flags Nova 4+ native Slug field and recommends testing the field's compiled assets on a branch rather than inferring support from the README.
- How do I generate a slug from a title field in a Nova resource?
- Add the field to your Nova resource and point it at the source attribute, for example Slug::make('Slug')->from('title'). The field then generates the slug inside the Nova form as editors type.
- Does drobee/nova-sluggable handle unique slugs and duplicate values?
- The field supports unique slug handling in the form, but it cannot guarantee database-level uniqueness. Add a unique index on the slug column and a unique validation rule scoped to the resource ID. Concurrent creates remain a database concern.
- Is drobee/nova-sluggable a replacement for spatie/laravel-sluggable?
- No. drobee/nova-sluggable is a Nova form field, not a model-level slug engine. Keep a trait such as spatie/laravel-sluggable as the source of truth for slugs written by APIs, imports, seeders, and queues.
- Will it generate slugs for API writes, imports, and seeders?
- It only affects writes made through the Nova resource form. API writes, imports, seeders, and queue workers will not use this field unless the model has a slug trait handling them.
- Can I customize the slug separator and generation options?
- Yes. The package exposes a customizable separator and slug options for how the generated value is formatted. Check the package README for the exact option names and defaults before configuring it.
- Why is my Nova slug field blank or throwing console errors?
- Nova field packages ship prebuilt JavaScript and CSS, and assets compiled against a different Nova toolchain can render blank or throw console errors. Verify the resource form on a branch after installation, check the browser console, and pin a narrow compatible version.
- Does Nova already have a built-in Slug field?
- Nova 4 and later ship a first-party Slug field with source syncing. Before adding this dependency, document acceptance criteria and confirm the native field cannot satisfy them.
- Is drobee/nova-sluggable maintained and safe for production?
- Treat it as a small, narrow dependency: it had a May 2024 release, roughly 45 stars, and zero dependents in the evaluation, so there is little community backstop. Verify rendering and compatibility on your Nova major, and decide in advance whether upstream, a fork, or a reimplementation owns it when Nova 5 arrives.