You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Hi there, Andrew from supabase, we've been having report of users failing to use supabase CLI with Deno 2 and running into some error executing the compiled binary.
To Reproduce
Steps to reproduce the behavior:
Have Deno 2 installed
Create a new directory, and run deno init in it
The following content been added to deno.json
{
# install deps in a node_modules directory "nodeModulesDir": "auto",
"imports": {
"supabase": "npm:supabase@^1.223.10"
}
}
Install deps: deno install --allow-scripts
Try run the CLI with deno run -A npm:supabase --help
Sees the following error in terminal:
❯ deno run -A npm:supabase --help
error: Uncaught SyntaxError: Invalid or unexpected token
at <anonymous> (file:///Users/folder/node_modules/.deno/[email protected]/node_modules/supabase/bin/supabase:1:1)
Debug:
Running /Users/folder/node_modules/.deno/[email protected]/node_modules/supabase/bin/supabase properly execute the binary.
Expected behavior
Deno 2 with deno run command should also be able to run the supabase CLI
Describe the bug
Hi there, Andrew from supabase, we've been having report of users failing to use
supabase
CLI with Deno 2 and running into some error executing the compiled binary.To Reproduce
Steps to reproduce the behavior:
deno init
in itdeno.json
deno install --allow-scripts
deno run -A npm:supabase --help
Sees the following error in terminal:
Debug:
Running
/Users/folder/node_modules/.deno/[email protected]/node_modules/supabase/bin/supabase
properly execute the binary.Expected behavior
Deno 2 with
deno run
command should also be able to run thesupabase
CLIAdditional context
Opening the issue based on discussion with @bartlomieju on discord: https://discord.com/channels/684898665143206084/1308818534809210930/1309145748264325120
Related: supabase/cli#2900
Version: Deno 2.0.6
The text was updated successfully, but these errors were encountered: