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
I tried to fetch the Typescript-scheme of my PostgresDB from a different scheme than "public"
and for some reason while running npm run supabase gen types typescript --project-id xyz -s "MyCustomSchemeAsNamedInPostgres" I am only allowed to receive the default scheme
and only by running it via npx: npx supabase gen types typescript --project-id xyz -s "MyCustomSchemeAsNamedInPostgres",
I receive the correct types for my specific scheme.
I dont know how the same tools can produce a different outcome on this.
Possibly this is a bug of npm itself.
To Reproduce
Pretty much both commands from above.
Both CLI-Versions being the same on v1.164.1.
Expected behavior
I expect my custom scheme to be generated as typescript-types in both cases.
Screenshots
At first by running it with npm run I have to select the project-id anyway - although it's already declared:
The actual type-Generation looks like this:
not being/containing the requested scheme.
If I run the same supabase-cli command via npx, it works as I intended it to:
It's notable, that every other supabase-cli-command I used so far is working as intended,
only the type-generation has this weird behaviour.
Thank you for your time and this great project!
System information
Version of OS: Ubuntu 22.04 LTS (WSL2)
Version of CLI: 1.164.1
Version of Docker: Docker version 25.0.3, build 4debf41
Additional context
The text was updated successfully, but these errors were encountered:
Describe the bug
I tried to fetch the Typescript-scheme of my PostgresDB from a different scheme than "public"
and for some reason while running
npm run supabase gen types typescript --project-id xyz -s "MyCustomSchemeAsNamedInPostgres"
I am only allowed to receive the default schemeand only by running it via npx:
npx supabase gen types typescript --project-id xyz -s "MyCustomSchemeAsNamedInPostgres"
,I receive the correct types for my specific scheme.
I dont know how the same tools can produce a different outcome on this.
Possibly this is a bug of npm itself.
To Reproduce
Pretty much both commands from above.
Both CLI-Versions being the same on v1.164.1.
Expected behavior
I expect my custom scheme to be generated as typescript-types in both cases.
Screenshots
At first by running it with
npm run
I have to select the project-id anyway - although it's already declared:The actual type-Generation looks like this:
not being/containing the requested scheme.
If I run the same supabase-cli command via npx, it works as I intended it to:
It's notable, that every other supabase-cli-command I used so far is working as intended,
only the type-generation has this weird behaviour.
Thank you for your time and this great project!
System information
Additional context
The text was updated successfully, but these errors were encountered: