Skip to content

edge-runtime fails to start a function whose service path is a symlink (Module not found) #701

@0x5457

Description

@0x5457

Bug report

  • I confirm this is a bug with Supabase, not with my own application.
  • I confirm I have searched the Docs, GitHub Discussions, and Discord.

Describe the bug

When a user worker is started via a service path that is (or traverses)
a symbolic link, edge-runtime fails to bootstrap the worker with:

worker boot error: Module not found: file:///var/tmp/sb-compile-edge-runtime/<...>//index.ts 2026-05-17T09:35:29.587764Z ERROR base::worker::driver: worker boot error: failed to bootstrap runtime: could not find an appropriate entrypoint

To Reproduce

In the repo:

cd examples
ln -s ./sse ./sse-link
cd ..
./scripts/run.sh   # main service: ./examples/main, port 1234
➜  examples git:(main) ✗ ls -l  | grep sse
drwxr-xr-x@  3 ubuntu  staff   96 Feb  6 14:36 sse
lrwxr-xr-x@  1 ubuntu  staff    5 May 17 22:06 sse-link -> ./sse

then

curl http://localhost:1234/sse        # works
curl http://localhost:1234/sse-link   # fails: "Module not found: .../examples/sse-link/index.ts"

Expected behavior

./sse and ./sse-link should behave identically; the worker should bootstrap successfully when reached through a symlinked service path.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    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