Add support for Supabase storage via S3 compatibility

4.0.0 (2026-02-25)

Full Changelog: v3.4.1...v4.0.0

Allow configuring supabase and migrate to FlyDrive 2.0

4.0.0-next.1 (2026-01-31)

Features

• allow configuring supabase storage as well (da37b14)

Full Changelog: v4.0.0-next.0...v4.0.0-next.1

Target v7

4.0.0-next.0 (2025-09-10)

Full Changelog: v3.4.1...v4.0.0-next.0

Improvements to file.moveToDisk method

We have exposed another option named moveAs to decide how to copy the file from the tmpPath to the remote disk. The action could be.

• stream: Perform a move operation via disk.moveFromFs method https://flydrive.dev/docs/disk_api#movefromfs
• buffer: Create a new remote object using disk.put method. This method will first read the file contents into a Buffer and then write it to the destination. This is the only method that works with SupaBase storage

Example:

router.post('/', async ({ request, response }) => {
  const file = request.file('file')
  if (!file) {
    return response.abort({ message: 'No file uploaded' })
  }

  const filename = `${cuid()}.${file!.extname}`

  // Read the file as a buffer and then write it. Supabase works with this
  await file.moveToDisk(filename, 'spaces', { moveAs: 'buffer' })

  // Write file by streaming it. This is the default behavior
  await file.moveToDisk(filename, 'spaces', { moveAs: 'stream' })

  return file
})

3.4.1 (2025-03-19)

Full Changelog: v3.4.0...v3.4.1

Introduce readThenWrite option when moving multipart files

3.4.0 (2025-03-19)

Features

• introduce readThenWrite action (0304b2c)

Full Changelog: v3.3.0...v3.4.0

Bug fixes and allow moving files to a disk using different actions

Earlier the moveToDisk method did not mark the file as moved, which resulted in not having access to the fileName and the filePath properties. That has been fixed now.

Also, we have exposed another option named moveAs to decide how to copy the file from the tmpPath to the remote disk. The action could be.

• stream: Perform a move operation via disk.moveFromFs method https://flydrive.dev/docs/disk_api#movefromfs
• buffer: Create a new remote object using disk.put method. This method will first read the file contents into a Buffer and then write it to the destination. This is the only method that works with SupaBase storage

3.3.0 (2025-03-19)

Bug Fixes

• handle writeOptions when diskNameOrOptions is provided (#55) (cbc7601)
• mark file as moved after moving it via moveToDisk method (e569c11)

Features

• allow streaming file via moveToDisk (8209dfa), closes #56

What's Changed

• fix: handle writeOptions when diskNameOrOptions is provided by @kamilcglr in #55

New Contributors

• @kamilcglr made their first contribution in #55

Full Changelog: v3.2.0...v3.3.0

Configure fakes

• feat: configure fakes deff46c

Full Changelog: v3.1.2...v3.2.0

Fix provider to extend MultipartFile

• fix: call method to extend MultipartFile be96735

Full Changelog: v3.1.1...v3.1.2

Small configure script improvements

• fix: syntax for extracting exact values for schema enum a4b79fb
• refactor: rename env variables and do service name to spaces 7b14759
• chore: update dependencies 97d3dba
• chore: update package metadata c0edd0d
• fix: define enum schema options as a const 6070ddd

Full Changelog: v3.1.0...v3.1.1

Improve configure script and add file.moveToDisk method

The file.moveToDisk method moves a user-uploaded file to one of the Drive disks.

Commits

• refactor: fix DO env vars and add R2_ENDPOINT env var eb9c5a9
• feat: configure default disk via DRIVE_DISK env variable 2c0050c
• feat: install peer depedencies during configuring b41864b
• feat: add MultipartFile.moveToDisk method to the bodyparser 5659418

Full Changelog: v3.0.0...v3.1.0