- What is nuewire/media used for in Laravel?
- According to the package overview, nuewire/media is a lightweight Laravel package for managing media and file uploads. It lets you attach images and files to Eloquent models, generate thumbnails and conversions, and store assets on local or cloud disks through a fluent API. It is part of the Nuewire Laravel suite, but the evidence available here is limited to the overview and a 1.0.1 release note.
- How do I install nuewire/media with Composer?
- Install it with Composer using the package name nuewire/media, then follow any service-provider or configuration publishing steps documented in the repository. The supplied evidence does not include the composer.json require block or installation instructions, so confirm the exact command and Laravel auto-discovery behavior from the repository before adding it to an application. A scratch Laravel app is the safest place to validate installation first.
- Which Laravel and PHP versions does nuewire/media support?
- The supported Laravel and PHP ranges are not stated in the evidence provided. Check the package composer.json require block and the repository README for explicit version constraints, and verify that your current Laravel LTS and PHP version are covered. Do not assume support from the 1.0.x version number alone.
- Does nuewire/media work with cloud storage like S3?
- The package overview says assets can be stored on local or cloud disks, which suggests it uses Laravel's filesystem disk abstraction rather than a single hard-coded storage backend. Confirm the exact disk configuration and any required adapter packages in the repository documentation. Test uploads, URL generation, and deletion against your target cloud disk before relying on it.
- How does nuewire/media compare to Spatie Media Library?
- Both appear to address attaching media to Eloquent models, but the available evidence for nuewire/media is much thinner than for Spatie Media Library. Key comparison points are supported Laravel versions, storage abstraction, image conversion dependencies, migration behavior, and production adoption. Evaluate nuewire/media with a spike and compare the generated schema and API surface directly.
- Can I generate thumbnails and image conversions with nuewire/media?
- The package description states that it can generate thumbnails and conversions, which implies some image transformation capability. The evidence does not identify whether it depends on Intervention Image or another library, or whether conversions run synchronously or in a queue. Verify the dependency tree and processing model before using it for large uploads.
- Does nuewire/media publish migrations, and will they conflict with my schema?
- The available evidence does not confirm whether the package ships migrations, whether they are publishable, or whether table names are fixed. Check the repository for database migrations and review the table names against your existing attachments or media schema. In a spike, run the migrations and rollbacks to confirm they are reversible.
- Is nuewire/media production-ready at version 1.0.1?
- A 1.0.x release indicates the maintainer considers the public API stable, but 1.0.1 with no release narrative gives little evidence of production exposure. The technical assessment flags adoption maturity, bus factor, and changelog traceability as open risks. Treat it as a candidate for a controlled spike rather than an assumed production dependency.
- What changed between nuewire/media 1.0.0 and 1.0.1?
- The supplied release notes for 1.0.1 contain only an auto-generated compare link and no description. That means the change could be a bug fix, a documentation update, or a silent behavior change, and the evidence does not distinguish between them. Ask the maintainer or inspect the diff before upgrading.
- How should I test nuewire/media before using it in a Laravel app?
- Stand up a throwaway Laravel app at the version you actually run, install nuewire/media, and attach and retrieve a file through a non-production model. Exercise local and cloud disks, thumbnail generation, migration rollback, and any queued processing you intend to use. Keep the spike isolated so you can evaluate reversibility without touching a real product branch.