- What is chaseconey/nova-external-image used for?
- It is a Laravel Nova field that renders external images from absolute remote URLs inside Nova resources. You store the image link on a model attribute and the field displays a preview in index, detail, and form views. It is presentation-only, so it does not upload, store, cache, proxy, or transform media.
- How do I install chaseconey/nova-external-image?
- Run composer require chaseconey/nova-external-image in a project that already has a licensed Laravel Nova installation, then declare the package's field class in the fields method of each Nova resource that needs it. There are no migrations, storage disks, queues, or domain services to configure. Because Nova is a private paid Composer package, installation must be proven inside a real Nova app rather than at the CLI.
- Which Laravel, Nova, and PHP versions does it support?
- Check the package's composer.json constraints before adopting, because the last tagged release was December 2023 and declared ranges may lag behind your current Nova, Laravel, and PHP versions. Compatibility with your specific production Nova line can only be confirmed in a staging install with browser verification. Nova frontend asset breakage after a major upgrade can fail silently, so a CLI success is not evidence.
- Does this field upload or store images locally?
- No. The field only renders a URL that is already persisted on your model, and image ownership, lifecycle, and invalidation stay with the external system such as a CDN, DAM, headless CMS, or product feed. It is not a media pipeline, upload workflow, or transformation tool and should never be treated as the system of record for image assets.
- How do I configure image sizing and display options?
- The field exposes configurable sizing and display options so you can control how the remote preview appears in Nova. Apply them when declaring the field in your resource, following the package README. Keep the configuration minimal and documented, since this is a small single-maintainer utility.
- Does it work in Nova index, detail, and form views?
- Yes, the field is designed to render inline previews across Nova's index, detail, and form views using the stored absolute URL. Verify each view in a browser during your compatibility spike, because Nova frontend asset pipeline changes can affect rendering without producing CLI errors.
- Can I use it for CDN, Gravatar, or headless CMS images?
- Yes, that is the intended use case: any absolute remote URL for an asset your application does not own locally, such as a CDN image, Gravatar avatar, DAM or PIM export, or product feed image. Make sure the host is reachable from staff browsers and allowed by your CSP, egress, and external-host allowlist policies.
- Does removing the field delete the remote image?
- Treat deletion as a silent no-op. Because the field extends Nova's Image field, the inherited delete logic assumes a disk-relative path, so an absolute URL will not be removed from the remote host. Handle cleanup and lifecycle in the external system that owns the asset, and disable delete behavior in the Nova UI where appropriate.
- Are there security concerns with rendering remote images in Nova?
- Confirm in code review whether rendering is purely browser-side; if so, enforce CSP, HTTPS and mixed-content rules, hotlinking rules, and an external-host allowlist for the images your admins load. If any server-side fetch exists in the code path, review it for SSRF, timeout, and content-type validation exposure. Also consider admin-tracking and privacy exposure from third-party image hosts.
- Is it maintained, and what are the alternatives?
- The package has a single maintainer, roughly 28 stars, zero dependents, no visible test suite, and a last release in December 2023, so classify it as a low-criticality admin convenience dependency. Pin the version, run a compatibility spike against your Nova line, and document a fallback such as a built-in URL or Image field with a formatter or a roughly one-day custom Nova field. If a reviewer workflow becomes business-critical, own the field instead of depending on it.