Relative import path in function regression

[Siilwyn]

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

From version supabase 2.67.1 relative imports that use tsconfig paths or deno.json imports seem to fail. They work in version 2.67.0.

To Reproduce

For example:

import { Webhook } from 'standardwebhooks';

And:

{
  "imports": {
    "standardwebhooks": "npm:standardwebhooks@1.0.0"
  }
}

Fails on npx supabase functions deploy with:

Error: failed to create the graph

Caused by:
    Relative import path "standardwebhooks" not prefixed with / or ./ or ../

Expected behavior

Imports are resolved.

[nathanschram]

Looks like a regression from supabase/cli#4619 which landed in v2.67.1. I traced it to a specific change in the CLI source.

The bundler now has a ShouldUseDenoJsonDiscovery() check that skips passing the --import-map flag to edge-runtime when your import map is named deno.json and sits in the same directory as the entrypoint:

if len(importMap) > 0 && !ShouldUseDenoJsonDiscovery(entrypoint, importMap) {
    args = append(args, "--import-map", importMap)
}

The intent was to rely on edge-runtime's auto-discovery of deno.json, but it doesn't actually resolve the imports map that way - so bare specifiers like "standardwebhooks" fail because nothing maps them to their npm: targets.

For now, pinning to v2.67.0 should get you unblocked:

npx supabase@2.67.0 functions deploy

Alternatively, renaming your import map to import_map.json (instead of deno.json) bypasses the check since ShouldUseDenoJsonDiscovery only triggers for deno.json/deno.jsonc. That only works if you don't need other deno.json config though.

[nathanschram]

Hey, just checking if pinning to CLI v2.67.0 resolved the import path issue? Happy to dig deeper if you're still seeing it on newer versions.

[Siilwyn]

Hey @nathanschram yes pinning to v2.67.0 works! It also works with tsconfig paths which newer versions don't seem to resolve either. Sorry for the late reply I'm not working on this project anymore and left it at 2.67.0, but supporting bare imports and import paths seem like a regression more people would encounter...

[Hallidayo]

Transferred from the supabase/supabase repo.