Basically, in the original function, I wrote 'profile' instead of 'profiles', which screwed everything up...

Nevermind, I made it work! For people facing the same issue: go to database and then go to database triggers/functions, you can find the deleted function there and edit it

WHY IS SUPBASE AUTH NOT WORKING

js
export async function signInWithGoogle() {
  const { user, session, error } = await supabase.auth.signIn({
    provider: "google",
  });
}

Property 'signIn' does not exist on type 'SupabaseAuthClient'.

I am getting the above error for

signIn

, can anyone tell me why?

Ur probably on v2

Yeah if you're using V2 RC, make sure you look at the correct documentation https://supabase.com/docs/reference/javascript/next/ Or simply use the V1 version

Can you elaborate in #1006358244786196510 please? Will be easier to see your issue

is realtime broadcast only available in v2 sdk?

I could be wrong, since I don't have the data. But it seems like the help channel, since switching over to posts, is less effective.

It seems more questions go unanswered now, and it is also a bit harder to ask questions.

Perhaps a change could be considered after collecting the data and surveying the community.

Could you elaborate on the "harder to ask" part? As far as more go unanswered, my biggest observation, and I've read every question here for 9 months, is after the last launch week Supabase has lots of new stuff that fewer people have experience with. New CLI stuff, new realtime features, vault, v2, more people trying edge function, etc. And since this is mainly a user answering user forum, there are fewer people who know the answer. But I'm sure the mods will discuss this. Thanks

I think it's harder to ask questions because there's a kind of context switch between asking a question in a chat forum and creating a post on a Q and A forum like Stack Overflow, which the new UI kind of mimics. So there's some pressure on the user to create a "post" rather than ask a question. Often times that barrier is confounding a few reasons, one being that the post format might seem intimidating when a user doesn't really know where to start. I also think it reduces answering because conversations are harder for the online population to skim over and provide feedback where they have experience.

It could all just be my experience though, so I don't know what others are experiencing or saying.

holy if I knew there were v2 docs that would've saved me so much pain 😭

On the other hand it keeps conversations easier to follow, less noise in chat, and makes the questions easier to skim thanks to the title. Also means I can better decide whether I can help answer a question without having to chase fragments of a conversation. And if I’m being honest, having people pause to think for how to ask for help hopefully leads to more fully formed and help-able questions

I agree with that perspective. It is better in a handful of ways.

How long should it take for a developer to setup the backend using supabase?

Is it normal that the docs have a serif font?

Hi It's fast. Supabase is a Postgres wrapper, so you only need to make some configuration (e.g change email templates) and setup the tables

No it's not normal, can you try to refresh the page without the cache please? (ctrl + maj +r)

I see it in a private window to (which does not use a cache).

I also see that line of CSS in the repository.

OK after I clear the cache I still see it.

I think

'serif'

should be removed there...

This is weird, because i'm not having this issue (private window too)

I'm on Linux, that may have something to do with it...

But

'serif'

is first in the list so I think the Linux behavior is correct...?

It could be a problem with Linux indeed, but this is weird tho, because i'm also on Linux xD