-
Notifications
You must be signed in to change notification settings - Fork 321
Open
Description
Describe the bug
Serving or deploying functions does not work. Supabase CLI can't access the files?
To Reproduce
Steps to reproduce the behavior:
- Create an Edge function using
supabase functions new test supabase functions serve- Try to call the function
- Error:
worker boot error: failed to bootstrap runtime: failed to determine entrypoint
- try to deploy:
$ supabase functions deploy test --debug
open supabase/.temp/profile: no such file or directory
Using access token for profile: supabase
Loading project ref from file: supabase/.temp/project-ref
Supabase CLI 2.58.5
Using profile: supabase (supabase.co)
Using access token for profile: supabase
2025/11/12 17:35:30 HTTP GET: https://api.supabase.com/v1/projects/jmmlkjbaxrbbfdugwtqr/functions
Bundling Function: test
Specifying import_map through flags is no longer supported. Please use deno.json instead.
Specifying decorator through flags is no longer supported. Please use deno.json instead.
Error: entrypoint path does not exist (supabase/functions/test/index.ts)
error running container: exit 1
Expected behavior
For the cli to find the files. I changed nothing in the created function.
System information
Rerun the failing command with --create-ticket flag.
- Ticket ID: 41e5a8de63984b738bb4f2e2e6dde0a9
- Version of OS: Fedora 42
- Version of CLI: 2.58.5
- Version of Docker: 28.5.1, build 2.fc42
- Versions of services:
SERVICE IMAGE | LOCAL | LINKED
------------------------|------------------------|------------
supabase/postgres | 17.6.1.005 | 17.6.1.005
supabase/gotrue | v2.182.1 | v2.182.1
postgrest/postgrest | v13.0.5 | v13.0.5
supabase/realtime | v2.63.0 | -
supabase/storage-api | v1.29.0 | -
supabase/edge-runtime | v1.69.23 | -
supabase/studio | 2025.11.10-sha-5291fe3 | -
supabase/postgres-meta | v0.93.1 | -
supabase/logflare | 1.25.3 | -
supabase/supavisor | 2.7.4 | -
Metadata
Metadata
Assignees
Labels
No labels