Hi there. I am unable to install @supabase/auth-helpers-nextjs from yarn. When I run

yarn add @supabase/auth-helpers-nextjs

, I get the error

An unexpected error occurred: "https://registry.yarnpkg.com/@supabase%2fauth-helpers-nextjs: Not found"

. What can I do?

Thanks. I guess I’ll update the README to include this then.

Hello everyone, when i query auth user i got null, how to get data

If you mean thru js or the api, you can't for security reasons. You can write an rpc security definer function to do that, or create a public profile table with a trigger function when a user is added. https://supabase.com/docs/guides/auth/managing-user-data

How do I get the user to be saved between sessions?

Hey there! I'm looking at realtime, but am unable to make it work.

const sub = this.$supabase
   .from("actions")
   .on("*", (data) => {
     console.log(data);
   })
   .subscribe();

  console.log(sub);

My subscription look like this. The

console.log(sub)

shows that's it's seems to be ok and

joined

- Replication on my table is enabled, I can see under the websocket tab the events occuring, and i can see the subscription being created under the realtime schema in the Supabase Table's UI. So everything seems good, but i'm never reaching the callback. Nothing happen. I though it could be because of some RLS rules, but even with it being disabled on my table, nothing. Stack in Nuxt 2.x and this is inside a

mounted

method on my

Index

page. And i'm using my anon/public key Any idea? 🙏

realtime not working

Hi there how do I use

getUserByCookie

(using nextjs)

Here you can find some nice example for nextjs auth. https://github.com/supabase/supabase/tree/master/examples/nextjs-with-supabase-auth Also you can use, your own implementation

export const getServerSideProps: GetServerSideProps = async ({ req }) => {
 // Get our logged user
 const { user } = await supabase.auth.api.getUserByCookie(req);
 // Check if the user is logged
 if (user === null) {
  // Redirect if no logged in
  return { props: {}, redirect: { destination: "/auth/login" } };
 }
 // If logged return the user
 return { props: { user } };
};

is

getUserByCookie

a server-side to be used or client side to be used?

I cant seem to get

getUserByCookie

working

I checked

req.cookies

and the only cookies I got is google analytics

I cant seem to get

getUserByCookie

how would u mock session for testing? using React, rtl, jest

Hey folks, I'm wondering is there API doco for the objects returned by the supabase-js library?

Supabase API Doco

is there a way to increment a cell instead of reading it, incrementing it and writing it again?

is there a way to increment a cell

unit test with react, testing library and jest

Do you have good experience with testing? Are you able to give me feedback on my simple unit test? https://discord.com/channels/839993398554656828/973427221148614656

Heya there! I'm currently using prisma to handle the postgres database of my supabase project, and is there a way to do relation of the prisma model to the auth model of supabase? I did found this answer https://www.reddit.com/r/Supabase/comments/ukelkx/comment/i7pldhz/?utm_source=share&utm_medium=web2x&context=3 but I'm not really sure how to approach that

is it possible to filter files by 'id NOT IN' an array?

Not in

how do I select all columns where the column with type int is greater than value x ?

or can't I do that ?

Is it easy to intercept network request and tamper with a form data? I am thinking how necessary is that I have an additional server side validation.

If there's a malicious extension I think so. I think it's harder with a malicious script if it were to somehow be injected.

What sort of things do you need to validate? It can probably be done with RLS and/or postgres functions

I am hacking some quick stuff together, so of course the data structure is not ideal, but this is how it is: In database I have

pricerange_from

and

pricerange_to

. I fetch data, concatenate and display in a form select as range option values as such:

5-10

,

10-20

,

50-10

etc. Now user can update their profile by selecting a different price range. But I don't want them to choose a different range than given options. Of course only hackers will do that. But they could create their own option

100-200

and, as a result, update their

pricerange_from

and

pricerange_to

in the database to higher numbers than allowed.