Skip to content

bug: folder extraction not working #5086

@IdellHeaney

Description

@IdellHeaney

Describe the bug
supabase functions download <function_name> produces different local output depending on whether Docker is running. For functions that reference files from _shared, the downloaded function folder is incomplete when Docker is available.

In the failing case, the function itself is downloaded, but the expected shared files are not written to supabase/functions/_shared.

To Reproduce

  1. Make sure Docker is running.
  2. Download a deployed function that imports files from ../_shared/....
  3. Inspect the downloaded files under supabase/functions/.
  4. Notice that the function folder is present, but the related _shared files are not.
  5. Stop Docker.
  6. Run the same supabase functions download <function_name> command again.
  7. Inspect the same location and notice that the _shared files are now present.

Expected behavior
The downloaded output should be the same regardless of whether Docker is running.
If a function depends on files from _shared, those files should be present after download in both cases.

Metadata

Metadata

Labels

bugSomething isn't workingdockerPull requests that update Docker codefunctions

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions