- What is dmitrybubyakin/nova-medialibrary-field used for?
- It is a Laravel Nova field that integrates Spatie's Laravel Media Library into Nova resources. It lets you upload, attach, and manage media files directly from the Nova admin UI. Use it when your models already implement Spatie's media contract and you want a richer field than a plain file input.
- How do I install dmitrybubyakin/nova-medialibrary-field?
- Install it with Composer in a Laravel project that already has Nova and Spatie Media Library configured. Nova is distributed through Laravel's private repository, so your Composer setup needs credentialed access to Nova before this package can resolve. Then add the field to a resource's fields() method on a model that implements Spatie's media interface.
- Which Nova and Spatie Media Library versions are supported?
- The field targets Nova 4 and 5 and Spatie Media Library 10 and 11, with PHP 8.1 or newer. Pin the package version explicitly against your Nova major and Media Library major. Nova 4 and 5 differ in frontend runtime, so a field built for the wrong major can render blank rather than fail loudly.
- Does it support multiple media collections?
- Yes, the field supports managing media across multiple Spatie Media Library collections. Collections are defined on your Eloquent model through Spatie's package, then exposed in the Nova field configuration. Documentation around multi-collection behavior is thin, so verify your exact combination of collections and field options in a staging resource.
- Can I use image conversions and responsive images with this Nova field?
- Image conversions are supported because Spatie Media Library performs the conversion work and the Nova field presents those media items. Responsive images and custom properties are less clearly documented, so confirm support for your Media Library version before relying on them. Test conversions against your disk and queue configuration in staging.
- Do I need Node or npm to use this Nova field?
- No, the package ships compiled Vue assets for the Nova frontend. Consumers do not need a Node toolchain to use the field, which is an operational simplification compared with source-distributed Nova tools. You may still need Nova's usual asset publishing workflow.
- What are the PHP and Laravel requirements for nova-medialibrary-field?
- It fits Laravel applications running Nova 4 or 5 with PHP 8.1 or newer. It works alongside Spatie Media Library 10 or 11 and local or S3 disk storage. Your application must already have Nova installed and models using Spatie's media traits.
- Is nova-medialibrary-field actively maintained?
- The package had a release on 2025-08-01, so it is not abandoned. It is maintained by a single maintainer and has no deprecation policy, LTS commitment, or vendor SLA. Check issue and pull request responsiveness over the last twelve months rather than relying only on the latest release date.
- What alternatives exist if I do not use this Nova field?
- The main fallback is Nova's plain File field plus custom media handling around Spatie Media Library. You can also build a small custom Nova field if you need tailored collection, conversion, or custom-property behavior. If you are not using Nova at all, this package is irrelevant and Spatie Media Library should be used directly.
- How should I test this field before using it in production?
- Test in a staging Nova application with the same Nova major, Media Library major, disk configuration, and conversions you plan to use. Check index-view thumbnails and peek behavior for N+1 query issues, and verify MIME validation, disk permissions, and path handling. Because documentation is thin and CI posture is unclear, rely on your own integration tests before rollout.