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
I'm giving Deno a spin as my main development tool to replace node/npm. I'm trying to run Supabase CLI with it and failing.
I have a package.json:
{
"devDependencies": {
"supabase": "^1.207.9"
}
}
Then doing :
deno install --allow-scripts
And here is the output:
Warning Trying to set up 'supabase' bin for "/Users/jgoux/Code/supabase-workflows/node_modules/.deno/[email protected]/node_modules/supabase", but the entry point "/Users/jgoux/Code/supabase-workflows/node_modules/.deno/[email protected]/node_modules/supabase/bin/supabase" doesn't exist.
I think the issue is that the symlinks get only created before the postinstall scripts run, which is an issue for CLI that get downloaded in postinstall scripts like Supabase one.
Another issue is that even if I create the symlink myself, deno run is failing:
ln -s /Users/jgoux/Code/supabase-workflows/node_modules/supabase/bin/supabase node_modules/.bin/supab
ase
deno run -A supabase --version
Output:
error: Is a directory (os error 21)
For this one I suppose it's because in a regular Supabase project, you create a supabase directory at the root of your project. And deno run is prioritizing this folder over the binary in node_modules/.bin/supabase.
To resolve this it would be better to priorize binaries over folders, or have a dedicated exec subcommand to run binaries explicitly?
The text was updated successfully, but these errors were encountered:
Thanks for reporting! I can reproduce the issue and confirmed it's something we should handle. I've opened a PR that should resolve the issue.
With regards to this part:
Another issue is that even if I create the symlink myself, deno run is failing:
It's not at all clear from the error message, but we don't currently support running binaries provided by npm dependencies in that way. You can run them directly like
./node_modules/.bin/supabase --version
or we support running binaries via scripts, so you can work around this with a script like
{
"scripts": {
"supabase": "supabase"
}
}
and then execute it with
deno task supabase --version
or
# note that this is running the script, which runs the binary
deno run supabase --version
Though I agree that it would be good to have something like npm exec for this
Version: Deno 2.0.4
Hello folks,
I'm giving Deno a spin as my main development tool to replace node/npm. I'm trying to run Supabase CLI with it and failing.
I have a package.json:
Then doing :
And here is the output:
I think the issue is that the symlinks get only created before the postinstall scripts run, which is an issue for CLI that get downloaded in postinstall scripts like Supabase one.
Another issue is that even if I create the symlink myself,
deno run
is failing:Output:
For this one I suppose it's because in a regular Supabase project, you create a
supabase
directory at the root of your project. Anddeno run
is prioritizing this folder over the binary innode_modules/.bin/supabase
.To resolve this it would be better to priorize binaries over folders, or have a dedicated
exec
subcommand to run binaries explicitly?The text was updated successfully, but these errors were encountered: