Add a Drive-style file manager to Next.js without giving up your bucket
file-next keeps the bytes in your S3 or R2 bucket and the folder tree in your database. Tenant comes from the server. The UI is optional. You already know how to put a file in S3. The trouble starts the week after. Someone wants folders. Then search. Then a trash can they can undo. Then a link they can send that does not expire into a raw bucket URL. Then a second customer, and the tenant id in…
file-next is an open-source filesystem for Next.js that keeps the bytes in your S3 or R2 bucket and the folder tree in your database. It provides a Drive-like explorer or allows you to use hooks without a UI. The metadata store can be SQLite or Postgres, while the object storage is S3 or R2. The filesystem separates the file management logic from the object storage, allowing for a more flexible and scalable solution.
File-next installs four packages: the base package, your own UI, a Drive-like explorer, and server actions. It uses getAuth() to determine the tenant ID and user ID securely, ensuring multi-tenant files are managed appropriately. The filesystem returns a Result object with success or failure information, making it easy to handle errors in your application.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
