- What is jameslkingsley/nova-media-library-field used for?
- jameslkingsley/nova-media-library-field is a Laravel Nova field for displaying and updating a Spatie Media Library model. It lets editors upload, browse, and select existing media attachments from Nova resource forms. It is narrowly scoped to applications already using both Laravel Nova and spatie/laravel-medialibrary.
- Is jameslkingsley/nova-media-library-field compatible with Laravel Nova 4 or Laravel 10/11?
- The package's last release was January 2019 and the repository is archived, so it almost certainly targets Nova 1.x/2.x-era APIs and older Laravel/PHP versions. There is no stated support for Nova 4 or current Laravel releases. Confirm the version matrix in composer.json and run a spike before assuming compatibility, because Nova is commercial and version-sensitive.
- How do I install jameslkingsley/nova-media-library-field?
- You would normally install it as jameslkingsley/nova-media-library-field via Composer, but because it is archived and last released in January 2019, do not add it directly to a modern production application. Treat installation as a time-boxed compatibility spike on a disposable branch and pin exact versions of Nova, Laravel, PHP, and spatie/laravel-medialibrary.
- Does it support single and multiple file uploads in Nova resource forms?
- The package is described as letting you upload, browse, and select existing media, but the context does not confirm whether it supports both single and multiple uploads on create and update forms. You must read the field source and test both behaviors explicitly in a Nova resource. Pay particular attention to create versus update forms and validation-error states.
- Do I still need to configure Spatie Media Library disks and collections?
- Yes. The field only manages the Nova form layer for media attachments; you still need to configure Spatie Media Library collections, storage disks, conversions, and authorization rules. Collection names and disk configuration are integration risks that the field does not remove. Keep your existing Spatie setup and test that the field respects it.
- Is jameslkingsley/nova-media-library-field safe to use in production?
- No, not as a direct maintained dependency for a modern Laravel/Nova stack. The repository is archived, adoption is low, and there has been no release since January 2019, so security and dependency drift are real concerns. If you must use it, fork it into a private package with an internal owner, tests, and a feature-flagged rollout.
- Is the repository still maintained or archived?
- No. The repository is archived and the last release was January 2019, so community support and issue triage are effectively absent. Without an internal fork, there is no upstream maintenance for compatibility with future Nova or Spatie releases. Budget for periodic dependency review and regression testing if you adopt the code.
- What alternatives should I evaluate to this Nova media library field?
- Evaluate maintained Nova media fields first, or build a small custom Nova field against the current Nova API if your needs are narrow. Because the package is only a Nova-plus-Spatie integration layer, you can often keep Spatie storage and collections unchanged while swapping the field UI. Compare maintenance ownership, Nova-version support, upload authorization, and deletion behavior before choosing.
- How do I fork jameslkingsley/nova-media-library-field and maintain it internally?
- Fork the repository into a private package, assign an internal owner, and add tests around the Nova resource screens you use. The codebase is small, so maintenance may be cheap, but you still own compatibility with Nova, Laravel, PHP, and spatie/laravel-medialibrary. Publish it internally with pinned dependencies and document collection conventions, disks, and rollback steps.
- How should I test upload authorization, validation, and media deletion before rolling it out?
- Run a time-boxed spike against Nova resource create, update, detail, and index screens, testing single and multiple uploads, disk and collection configuration, replacement, deletion, validation errors, and failed uploads. Verify upload authorization and confirm how orphaned media are cleaned up. If any incompatibility appears, stop and reassess rather than patching production ad hoc.