It would seem like raising exceptions don't get passed back down through the Supabase library, I'm trying to raise an exception on a trigger function on the

auth.users

table and the only error I'm getting is "Database error saving new user" while I was expecting the message from the exception to show instead.

Does your trigger run before or after the insert/update? I would assume that if it is after, you will NOT know about it but it will be strange if it is BEFORE the insert/update and you still get 200 on the REST call

It's before, this definitely has to do with how the API endpoint for signUp/signIn handles exceptions

I see - this doesn't make sense to me. Have you opened an Issue on GitHub?

Yeah I opened one https://github.com/supabase/gotrue-js/issues/170

Btw - what happens if the user clicks on the link that was still sent - I hope nothing (i.e. they are not confirmed since no record actually exists in the DB), right?

Yes correct, it will return a fragment in the url with error_code 404 and error_description "Confirmation Token not found"