Weave Code
File Laravel Package
amethyst/file
A lightweight file handling component for Amethyst that wraps Laravel's filesystem with a fluent API for uploads, disk paths, mime types, and file metadata. A clean, reusable building block for projects that need consistent file management.
At a glance
Frequently asked questions about File
- Is amethyst/file a Laravel package?
- No. amethyst/file is a component of the Amethyst PHP framework, not a Laravel package. It assumes Amethyst's service container, event dispatcher, and configuration conventions to resolve file handlers and emit lifecycle events. Laravel already provides equivalent primitives through UploadedFile, the Storage facade, FilesystemAdapter, and validation rules.
- Can I use amethyst/file in a Laravel application?
- You can attempt it, but integration feasibility is low. Standalone use would require pulling in Amethyst core contracts such as core, events, and config and wiring them into Laravel's container, which creates dual-container maintenance debt. The assessment recommends a replace, don't adopt posture for greenfield Laravel work and native file handling instead.
- What does amethyst/file actually do?
- It is a lightweight file handling component that wraps Amethyst's filesystem with a fluent API for uploads, disk paths, mime types, and file metadata. It is intended as a reusable building block inside Amethyst projects that need consistent file management. For Laravel developers, its capabilities overlap with UploadedFile, Storage disks, and validation rules, so it does not fill a clear gap.
- Does amethyst/file work standalone without the Amethyst framework?
- Likely not without significant glue. The package presumes Amethyst's container, event dispatcher, and configuration conventions, and no PSR-7 or PSR-17 interoperability is evident from its surface. Treat standalone consumption as a vendor, fork, and rewrite exercise rather than a normal dependency. Verify composer.json for hard requirements on amethyst/core, amethyst/events, and amethyst/config before considering it.
- How do I install and configure amethyst/file?
- The normal path would be composer require amethyst/file, followed by Amethyst-specific configuration for file handlers and disks. There is no indication of a Laravel service provider, config publishing, or native integration with config/filesystems.php. For Laravel, configure disks in config/filesystems.php and use the Storage facade instead. If you are only evaluating the package, install it in an isolated scratch service and record every container and event binding it requires.
- Does amethyst/file support Laravel 10 or Laravel 11?
- There is no declared Laravel version support because this is an Amethyst framework component, not a Laravel package. Its PHP 8.2 and 8.3 compatibility is also unproven until you verify the composer.json PHP constraint. Assume incompatibility with modern Laravel runtimes until proven otherwise. A missing PHP 8.2+ guarantee is a blocker for production Laravel use.
- What are the best alternatives to amethyst/file for Laravel file uploads?
- Use Laravel's native stack: Illuminate\Http\UploadedFile for uploads, the Storage and File facades for disk paths, FilesystemAdapter for filesystem operations, and validation rules such as file, mimes, max, and dimensions. These are more mature, better documented, and covered by Laravel's security release cadence. The assessment found no architectural seam where amethyst/file improves on these built-ins.
- Is amethyst/file maintained and safe for production?
- The assessment rates technical risk as high: 0 stars, 0 dependents, a composite score of 0, and a dormant upstream Amethyst framework. File-handling code is security-sensitive, and a dormant package means no upstream security patching for MIME sniffing, path traversal, or unrestricted upload issues. Transitive dependency rot is also probable. Do not use it in production Laravel without a fork-and-own commitment.
- How should I test or migrate a legacy amethyst/file integration in Laravel?
- Use a strangler pattern. Introduce your own FileHandler interface, implement it once against the Amethyst package and once against Laravel's UploadedFile plus Storage, route traffic through a feature flag, and run parallel validation on production-like file types. Decommission the Amethyst implementation only after parity is demonstrated. For greenfield code, reject the Amethyst package outright.
- Should I fork amethyst/file or rewrite file handling with Laravel Storage?
- For greenfield Laravel projects, rewrite with Laravel Storage and native validation; do not adopt amethyst/file. For legacy services that already depend on it, fork only if you can name an owner and commit to maintaining PHP version bumps, security fixes, and dependency updates. Otherwise close the initiative after a gap analysis shows zero or negative delta versus the native stack. The safer migration is the FileHandler adapter plus feature flag described above.
Weaver
How can I help you explore Laravel packages today?