[bug] functions deploy fails at bundling with 'An error occurred in Effect.tryPromise' (2.111.0, Windows); --use-api works

[ocjamison]

Summary

supabase functions deploy <name> fails in CLI 2.111.0 at the bundling step with a generic An error occurred in Effect.tryPromise. --debug adds nothing beyond the line below. The same function deploys fine with CLI 2.102.0, and with 2.111.0 when --use-api is passed, so the failure appears specific to the local Docker-based bundler in the newer code path.

This looks like the same class of opaque failure as #5892 (functions serve --env-file, fixed in v2.110.0-beta.36 via #5904), but on a different command and still present in 2.111.0.

Repro

npx -y supabase@latest functions deploy <name> --no-verify-jwt --debug

Output:

NotFound: FileSystem.readFile (C:\Users\<user>\.supabase\profile)
Using access token for profile: supabase
Supabase CLI 2.111.0
Using profile: supabase (supabase.co)
Using access token for profile: supabase
2026/08/06 15:01:49 HTTP GET: https://api.supabase.com/v1/projects/<project-ref>/functions
Bundling Function: <name>
{"_tag":"Error","error":{"code":"UnknownError","message":"An error occurred in Effect.tryPromise"}}

What works

• supabase functions deploy <name> --no-verify-jwt on CLI 2.102.0: bundles and deploys (script size: 4.293MB).
• npx -y supabase@latest functions deploy <name> --no-verify-jwt --use-api on 2.111.0: uploads assets and deploys successfully.

Same project, same function, same shell, back to back.

Possibly relevant

Docker is running and healthy (daemon 29.4.0, API reachable). The only edge-runtime image cached locally is public.ecr.aws/supabase/edge-runtime:v1.74.0, pulled by the older CLI. If 2.111.0 expects a newer image, a failed pull or container start would be my guess at what the Effect.tryPromise wrapper is swallowing. The error surfaces within a couple of seconds, with no pull progress printed.

Environment

• OS: Windows 11 Pro, 10.0.26200
• CLI: 2.111.0 (via npx supabase@latest); 2.102.0 installed standalone at %LOCALAPPDATA%\supabase-cli\ and working
• Docker: 29.4.0
• Function: Deno, single edge function with an npm-specifier import map (deno.json), 4 source files

Ask

Two things would have saved the debugging time here: surfacing the underlying error instead of UnknownError, and naming the bundler step that failed. The workaround is easy once found, but the message gives nothing to search on.