Skip to content

fix(functions): pass deno config as import map#5369

Closed
Subharup-31 wants to merge 1 commit into
supabase:developfrom
Subharup-31:fix/deno-json-import-map-bundling
Closed

fix(functions): pass deno config as import map#5369
Subharup-31 wants to merge 1 commit into
supabase:developfrom
Subharup-31:fix/deno-json-import-map-bundling

Conversation

@Subharup-31

Copy link
Copy Markdown

What changed

Pass the resolved import map to edge-runtime whenever one is configured, including deno.json and deno.jsonc files that live beside the function entrypoint.

This fixes the regression described in #5069 where bare imports from deno.json were no longer resolved during supabase functions deploy because the CLI skipped --import-map and relied on edge-runtime auto-discovery.

Why

The CLI already resolves the correct import map path before bundling. Passing it explicitly keeps legacy import_map.json behavior and restores deno.json/deno.jsonc import resolution for both native and Docker bundling.

Verification

  • GOCACHE=... GOMODCACHE=... go test ./function from apps/cli-go/pkg passed
  • GOCACHE=... GOMODCACHE=... go test ./internal/functions/deploy from apps/cli-go was attempted, but the runner volume ran out of temp build space while compiling dependencies before package tests could run

@Subharup-31 Subharup-31 requested a review from a team as a code owner May 27, 2026 20:04
@jgoux

jgoux commented Jun 24, 2026

Copy link
Copy Markdown
Contributor

Thanks for your contribution! 🙏

This bug was fixed during the TypeScript port of the command so I'm closing this PR.

@jgoux jgoux closed this Jun 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants