Weave Code
Ux Filemanager Laravel Package
mezcalito/ux-filemanager
A Laravel package that adds a ready-to-use file manager UI for browsing, uploading, renaming, and deleting files and folders on your configured storage disks. Ideal for admin panels, it offers a simple, customizable way to manage files without building CRUD screens.
mezcalito/ux-filemanager is a Laravel package that provides a clean, ready-to-use file manager interface for browsing and managing files in your application. It helps you add common file operations without building a custom admin UI, keeping file management simple and consistent.
- File browsing through a user-friendly interface
- Upload, rename, and delete files in one place
- Configurable storage paths and Laravel filesystem disks
- Easy integration into existing Laravel views
Frequently asked questions about Ux Filemanager
- Does mezcalito/ux-filemanager work with Laravel out of the box?
- No. mezcalito/ux-filemanager is a Symfony UX bundle built around Twig components, Stimulus controllers, Symfony dependency injection, and AssetMapper conventions. Laravel has no Twig rendering pipeline and does not load Symfony bundle extensions, so the package as shipped cannot be installed and used natively in a Laravel app. You would need to port the domain logic into Laravel services and rebuild the UI in Blade.
- How do I install mezcalito/ux-filemanager in a Laravel application?
- You should not add it to composer.json in a Laravel app expecting it to work like a Laravel package. The practical paths are to run it in a small Symfony sidecar service and call it over HTTP, or to vendor or fork the package read-only and extract the file service classes into app/Services. Rebuild the Twig views in Blade and replace Symfony DI wiring with a Laravel service provider.
- Which Laravel and PHP versions does mezcalito/ux-filemanager support?
- The package does not declare Laravel framework support because it is a Symfony UX bundle. Its composer.json pins Symfony components and PHP constraints that may collide with the Symfony packages Laravel already ships, such as HttpFoundation, Finder, and Mime. Check those constraints carefully and test in an isolated environment before assuming compatibility.
- Can I use Laravel Storage or Flysystem with this file manager?
- Laravel's Storage facade is a Flysystem 3 wrapper, so the underlying storage problem is shared with the package. The key question is whether the package's file operations sit behind an injectable filesystem interface or are hard-wired to a Symfony Flysystem service. If the storage layer is abstracted, writing a Laravel Storage adapter is a bounded task; if not, you will need to refactor before reuse.
- Do I need Twig or Symfony UX to use mezcalito/ux-filemanager?
- Yes for the shipped interface. The presentation layer depends on Twig templates, Symfony UX Turbo, AssetMapper assumptions, and Stimulus controllers, none of which are native to Laravel. You can keep the Stimulus controllers under a Vite build if their DOM contracts are clean, but the Twig views must be rewritten in Blade or replaced with Alpine or Livewire components.
- How do I implement file upload, browsing, and deletion in Laravel with this package?
- Treat the package as a reference implementation rather than a drop-in dependency. Extract the service and domain classes, re-home them under app/Services, and map them onto Laravel contracts such as Storage, Validator, and Gate or Policy for per-file authorization. Rewrite the routes as Laravel controllers and rebuild directory navigation and file operations in Blade views.
- Is mezcalito/ux-filemanager safe to use for production file uploads?
- File upload and browse handlers are security-sensitive, and this package is unaudited third-party code with a small user base. Review the upload validation path for path traversal, MIME sniffing, and arbitrary-write risks before exposing it to users. Add your own path canonicalization, extension and MIME allowlists, per-user quotas, and signed URLs for delivery.
- Can I reuse the Stimulus controllers with Vite in a Laravel app?
- Stimulus works fine under Vite, so the controllers are the most portable part of the frontend if they are self-contained. Check whether they rely on undocumented DOM contracts or Turbo-specific behavior before committing. If they are tightly coupled to Twig-rendered markup, rewriting the interactions in Alpine or Livewire may be faster than adapting them.
- What are the alternatives to mezcalito/ux-filemanager for Laravel file management?
- Look at Laravel-native file manager packages, Flysystem-based admin tools, or building a focused file browser with Livewire and Alpine. Another option is running this bundle in a small Symfony sidecar and calling it from Laravel, but that adds a second runtime and deployment pipeline for a file browser. At 22 stars and zero dependents, using it purely as a UX and edge-case reference is often the right call.
- Is mezcalito/ux-filemanager actively maintained, and what is the bus factor risk?
- The project is single-vendor under Mezcalito, and a release on 2025-12-08 shows it is alive, but the bus factor is effectively one. With around 22 stars and zero dependents, there is little downstream production validation to rely on. Treat it as a niche utility and plan to own any code you extract rather than depending on upstream fixes.
Weaver
How can I help you explore Laravel packages today?