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
- Make sure Docker is running.
- Download a deployed function that imports files from
../_shared/....
- Inspect the downloaded files under
supabase/functions/.
- Notice that the function folder is present, but the related
_shared files are not.
- Stop Docker.
- Run the same
supabase functions download <function_name> command again.
- 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.
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
../_shared/....supabase/functions/._sharedfiles are not.supabase functions download <function_name>command again._sharedfiles 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.