Supabase is an open source Firebase alternative. Start your project with a Postgres database, Authentication, instant APIs, Edge Functions, Realtime subscriptions, and Storage.

Supabase

all I see are type definitions that have no docs on them 😦

https://supabase.github.io/supabase-js/modules/lib_SupabaseQueryBuilder.html

https://supabase.github.io/supabase-js/classes/lib_SupabaseQueryBuilder.SupabaseQueryBuilder.html

or actually wait there are docs if you scroll more 🎊

also why do I not get types if I install the package

I did `npm install @supabase/supabase-js` then in code I get

https://supabase.github.io/supabase-js/classes/lib_SupabaseQueryBuilder.SupabaseQueryBuilder.html but here it is in the api

You seem to be referring to the main supabase-js client code.   Documentation is mainly here: https://supabase.com/docs/reference/javascript/supabase-client

Please start a thread if you add more to this.

https://supabase.com/docs/reference/javascript/supabase-client

there are links to libraries that make up supabase-js but thats all I see

perhaps you know or I misunderstand typescript

as https://supabase.github.io/supabase-js/modules/lib_SupabaseQueryBuilder.html this is not api or well its api for class but I never used them in TS

I recommend starting a new question with specific info you are seeking.  The guides have more info on the process also.

is there a way to run this example https://supabase.com/docs/reference/javascript/auth-signup using top level await?

getting this for

```
const { user, session, error } = await supabase.auth.signUp({
  email: 'nikita.voloboev@gmail.com',
  password: 'ar8Ke8thvz!Hm4!b9qs9qo*Q!a',
})
```

I have latest node version which is weird

https://github.com/egoist/tsno also this fixes it

I ran 

```
const {} = await supabase.auth.signUp({
  email: "my-email@gmail.com",
  password: "ar8Kevz!Hm4!b9qs9qo*Q!a",
});

const { user, session, error } = await supabase.auth.signIn({
  email: "my-email@gmail.com",
  password: 'ar8Kevz!Hm4!b9qs9qo*Q!a',
})
```

and my user is null. how can that be? I don't get error from signUp

maybe I don't get something about how supabase deals with users?

```
{
  id: '1c0bf776-4bd8-4482-bf7f-ada7aa866dd6',
  aud: 'authenticated',
  role: 'authenticated',
```

I get this if log the `user` from `signUp` call

Try checking out the docs:
https://supabase.com/docs/reference/javascript/auth-signup#notes
I think it may be the case for you
> By default, the user will need to verify their email address before logging in. If you would like to change this, you can disable "Email Confirmations" by going to Authentication -> Settings on app.supabase.io

`If "Email Confirmations" is turned on, a user is returned`

or wait I think I need to delete the user first to apply it

was trying to maybe getUser it to see if it exists 
https://supabase.com/docs/reference/javascript/auth-api-getuser

as for deleting it I need its service_role 

https://supabase.com/docs/reference/javascript/auth-api-deleteuser

something really strange is happening with the client as it now returns null for when I do

```
const {user} = await supabase.auth.signUp({
  email: "email-test@gmail.com",
  password: "ar8Ke8thvz!Hm4!b9qs9qo*Q!a",
});
console.log(user)
```

like here is screenshot, to right is output of code on left, I was getting user object but now its null

I guess because I switched the confirm email button but it makes no sense how thats related

Probably it is because you are trying to sign up user with the same email multiple times

You still can find a lot of information that may be really helpful with a lot of your questions in our docs:
for example here https://supabase.com/docs/learn/auth-deep-dive/auth-deep-dive-jwts
And in other articles in Auth section

Do we have a way to filter through a JSON array properties on Supabase ?

if the there's a Team table with a Monsters JSON array property, do we have a way to filter through the Monsters JSON array to find an element ?

https://supabase.com/docs/reference/javascript/select#querying-json-data
Which sends you to here for details: https://postgrest.org/en/stable/api.html#json-columns
And has an array example.

Yeah I saw that, but is it possible to query something like monsters->name (will filter through all names)

Possibly using contains with the json path to array and [‘value’] as parameter.

something like .contains('monsters->0', ['Monster name']) ?

Would need to point to the array is that 0?    No example I am just looking at docs.

the array is Monsters and it has 10 Items and each item has a Name property

What I was thinking was more for {"a":"b","names":["a","b","c"] }  so it would not work for {"Monstors":["item1:{"a":"b","Name":"Fred"}","item2":.....
if that is what you have..

Monsters JSON array is like this: [{ "id": "123", "name": "Mylor"}, { "id": "657", "name": "Grum"}]

It's in a table named teams : { id: "fqd67df", monsters: JSON }

the goal is to find the teams that contains a monster's name

Yeah, understand....  I don't have a guess at that.  
You might be better off with an rpc function and using Postgres methods.  I would google and see if you can find some examples in the broader Postgres world.
It has alot more json handling than the js client would.  
https://www.postgresql.org/docs/current/functions-array.html
You might post your example in sql thread here (showing your array points out the issue more quickly than your initial question.)  Maybe one of the SQL gurus might have an idea...

I won’t be using supabase for that use case but something like elastic search

I’m seeing something weird with the supaBaseClient sdk and it’s related to RLS. I’ve got the following policies defined on a table (see attachment) and I only get data back on initial load. If I refresh, I’m getting back an empty array. It definitely seems RLS related because when I temporarily disable RLS for that table — I get back results every time, even on refresh

You are probably accessing the table before supabase finishes checking and setting up the user from local storage if you are running just client code.  If you have server side code involved, other things can come into play.  You can use onAuthStateChange and log signin event to see if you are going out before you have a user.

I'm using the new `supabase-auth-helpers` 

```
import {
  withAuthRequired,
  getUser,
  User,
} from '@supabase/supabase-auth-helpers/nextjs'
```
then in my `getServerSideProps` I'm doing
```
export const getServerSideProps = withAuthRequired({
  redirectTo: '/sign-in',
  async getServerSideProps(ctx) {
    // Access the user object
    const { user } = await getUser(ctx)
    return { props: { user } }
  },
})
```

I'm getting a user back every time in my component though, so I'm not sure why this call w/ RLS is choking on me

My comment about if using server side stuff applies then and could be a number of things... But I don't do server side code in my project, so really not much help.
If no one else comes along, ask again in a new question mentioning supabase-auth-helpers in your comment.

it's okay I figured out the issue. Because I'm dealing with server side context I needed to call the `supabaseServerClient(ctx)` like so

```
const { data: member, error } = await supabaseServerClient(ctx)
      .from<definitions['member']>('member')
      .select('*')
      .eq('id', userId)
```

Does anyone know how to generate types for typescript?

I'm pretty sure you can import any you need

<@445287522843623424> 
```js
import { writeFileSync } from 'fs';
import openapiTS from 'openapi-typescript';
import dotenv from 'dotenv';

dotenv.config();

const url = 'your-supabase-url';
const key = 'your-supabase-anonkey';

// example 3: load [string] as remote URL (YAML or JSON; released in v4.0)
const output = await openapiTS(`${url}?apikey=${key}`, {
    version: 'v3'
});

writeFileSync('./src/lib/supabase.types.ts', output);
```

I have this script to generate the types, you can add a script in your package.json that executes it, I hope it works for you

```js
require("dotenv").config();

const fs = require("fs");
const gradient = require("gradient-string");
const path = require("path");
const ProgressBar = require("progress");
const { fetch } = require("cross-undici-fetch");

const {
  buildClientSchema,
  getIntrospectionQuery,
  printSchema,
} = require("graphql");

const supagradient = gradient(["#00CB8A", "#78E0B8"]);

function fetchGraphQLSchema(url, options) {
  options = options || {}; // eslint-disable-line no-param-reassign

  const bar = new ProgressBar("🔦  Introspecting schema [:bar]", 24);

  const id = setInterval(function () {
    bar.tick();
    if (bar.complete) {
      clearInterval(id);
    }
  }, 250);

  return fetch(url, {
    method: "POST",
    headers: {
      Accept: "application/json",
      "Content-Type": "application/json",
      apiKey: process.env.SUPABASE_ANON_KEY,
    },
    body: JSON.stringify({
      query: getIntrospectionQuery(),
    }),
  })
    .then((res) => {
      debugger;
      return res.json();
    })
    .then((schemaJSON) => {
      if (options.readable) {
        return printSchema(buildClientSchema(schemaJSON.data));
      }

      bar.complete();
      return JSON.stringify(schemaJSON, null, 2);
    });
}

const filePath = path.join(__dirname, "../graphql/schema/", "schema.graphql");

console.log();

console.log(
  supagradient(
    `🗞   Fetching GraphQL Schema from ${process.env.SUPABASE_URL} ...`
  )
);

fetchGraphQLSchema(`${process.env.SUPABASE_URL}/graphql/v1`, {
  readable: true,
}).then((schema) => {
  fs.writeFileSync(filePath, schema, "utf-8");
  console.log(supagradient(`✨  Saved to ${filePath}`));
  console.log(
    '💡  Be sure to run "yarn run codegen" to generate latest types.'
  );
});
```

https://tenor.com/view/capybara-cbt-capivara-chill-relax-gif-21621483

Getting a no matches found response following the docs

How can I redirect users after they have used magic link
For example:
Login page is at www.xyz.com

And when they click the magic link, they should be redirected to www.xyz.com/dashboard

Are there any parameter I have to add?

EDIT: This is likely wrong:   I don't use it but you should just be able to edit the email template:

you think if I add the path to the end of the {confirmationURL} it would take the person there?

You can't use redirectTo which is only used by 3rd party signin to send to a different page.

I may be wrong on the ability to add there...  The url may have session info attached already.

If so when signin event occurs in onAuthStateChange handler you could redirect...

Thank you so much. please can you break your explanation down.

This video shows an example: teed up with the onAuthStateChange.
https://youtu.be/oXWImFqsQF4?t=1301
When the user clicks on the link the supabase client code sees session info in the URL and signs in the user behind the scenes.  The onAuthStateChange handler then triggers a SIGNIN event.  In his code you can see he uses his frame works router command to redirect the page... you can also do the directly in javascript without a framework.

I did that but what happend was, it went to www.xyz.com then waited for a second before redirecting to www.xyz.com/welcome

Any time you come back from magiclink there is no user for the time it takes for the Supabase client to confirm the session data in the URL is valid at the server, then you get signin event.  Even on page refresh there is a short time as it loads from local storage the session and processes it.

I also see this in the Supabase signin doc notes:
```
If you provide email without a password, the user will be sent a magic link.
The magic link's destination URL is determined by the SITE_URL config variable. To change this, you can go to Authentication -> Settings on app.supabase.io
```
Seems a bit odd as on the server that is called: SiteURL -- The base URL of your website
But you can also try it, especially if you are only do magic link, to force it to dashboard page, but you would still have no user for a brief time so can't start database calls immediately...

This is very true.
I will watch the video you sent and I will also look for ways to manage it.

I think if an additional parameter is added to the magic link signin function, it would help redirect users (although this would open web apps to a lot of security issues)

Thank you Gary, 
I am grateful

<@375459781965512714> How would that set an alternate path for magiclink?  I think that is a list to validate various redirect links so they can't be "faked"  and is mainly used for 3rd party auth providers as mentioned under the field.    Email/Password and magiclink (email only) don't use the redirectTo link in SignIn call.   I could be wrong though as I don't use magiclink.

I used the following template

```
<h2>Account Recovery</h2>

<p>The link below will automatically log you back into my Awesome app:</p>
<p>
  <a
    clicktracking="off"
    href="{{ .SiteURL }}/member/sign-in/#recovery_token={{ .Token }}"
    >click here to recover your account</a
  >
</p>
```

the important parts here or `{{ .SiteURL }}` and `#recovery_token={{ .Token }}`

that `{{ .SiteURL }}` comes from this settings page

I think this is wrong, you can use redirectTo with magic link.

```
if (env === "prod") {
    const { data, error } = await supabase.auth.signIn({
email });
  } else {
    const { data, error } = await supabase.auth.signIn(
      { email },
      { redirectTo: "http://localhost:3000" }
    );
  }
```

I use something like this to send my magic links to localhost for development

`redirectTo` on the signIn is the way to go.

May need another doc update...

Sign in with redirect.#

Note that the redirectTo param is only relevant for OAuth logins, where the login flow is managed by the Auth server. If you are using email/phone logins you should set up your own redirects (within the email/sms template).

Oh wow, I'm almost certain I've used it in the past with magic link. But Kang Ming would know best as thats his domain.

<@591565850838827008> We have confirmation the documentation is not accurate and redirectTo does work for password less email magiclink.
https://github.com/supabase/supabase/issues/6534  If you go back to retry and have issues again please bring it up.

Anyone have an idea why upload using base64 is not working on react native web, but works on react native app?

Actually it successfully uploads but the images are becoming blank images

Hey guys, I have a question, about using SUPABASE PROVIDER AUTH in nextjs. When I want to authenticate, supabase redirects me to a url that doesnt exist. Is there any way to signin with popup, or to fix te issue.

You probably want to add a redirectTo property to your Auth component:

For my dev version I just have localhost in my .env.local like this:

```
# OAuth redirect URL
OAUTH_REDIRECT_TO=http://localhost:3000/
```

Is there a way to get random rows using Supabase .js? Like, select 100 rows from a table but randomized/shuffled?

Not really unless you brute force 100 random id's in an .in filter.  An rpc function returning multiple rows with a select * from table order by random() limit 100;  
But you should google "postgres random()" as evidently there are performance issues with larger tables.