Hi Try

js
const { data, error } = await supabase
  .from('cities')
  .select('name', 'country_id')
  .order('RANDOM()', { ascending: false })

you can't use Node built-ins inside of

_middleware.js

, as it runs in a different runtime. You can't use

fs

, this is why this is happening. https://nextjs.org/docs/api-reference/edge-runtime#unsupported-apis Is your

@/config/index

import reading from the filesystem? if it is, you will need to change up however you are loading config values. Perhaps use environment variables instead if you're trying to configure supabse from a config file. Can't give you a better answer without more context

Also I see you are trying to to check if the user has a session with

getUserByCookie

and redirecting them if they don't, have you tried the

withMiddlewareAuth

function from

@supabase/auth-helpers-nextjs/middleware

instead? Because it provides the same functionality. Here's a usage example from the docs: https://github.com/supabase-community/auth-helpers/tree/main/packages/nextjs#protecting-routes-with-nextjs-middleware

hey, i tried that no luck.

I created a view like this:

@Günhan The view is the way or an rpc function. PostgREST does not support random(). https://github.com/PostgREST/postgrest/issues/2257 Just remember you need to add your own where policy as view will bypass RLS.

Is there any way i could debug this message better? Context: im getting the magiclink token from email and redirecting back to my app and using verifyOtp();

const verify = await supabase.auth.verifyOTP({
            email: 'emailtest@gmail.com',
            type: tokenType,
            token: token
        });

Object {
  "error": Object {
    "message": "Request Failed",
  },
  "session": null,
  "user": null,
}

magiclink and verifyOtp()

Raw SQL request from SDK

Thanks a lot!

The

@/config/index

is basically a configured module alias (https://nextjs.org/docs/advanced-features/module-path-aliases) (to import the

index.js

file in the

config

folder) in a

jsconfig.json

file. I guess it uses the

fs

module internally, perhaps that's what is causing the issue. I'll try with a standard import and see if that helps.

Thank you @saeris , appreciate your help. It's great to be in a community where you get so much support, makes building a lot easier.

Hey there! I wanted to look around about using and accessing data from supabase with its REST-API URL ,So just wanted to ask that in api docs it shows to use headers - API key & Authorization but its value is SUPABASE_KEY , So exactly what is this Key, am bit confused there which key to use?

These are your key's and url: You use anon key on the client and if you need higher level access can use the service_role key on a server.

So i'll need to use service_role key? as am writing server-side code to access supabase db

You don't have to use service_role, on server. It just depends on what you are doing with passing client jwt's and your RLS setup or what auth functions you might call.

P.S - am using Sveltekit

Oh got it

Thanks,Its all clear now👍

Hi every body today need help to select only one of customer_room that has status rented

oh I was found solution. is it best practice ?

Hi we re just getting started and we re

Hello, I am trying to implement LinkedIn authentication on my project. I have created an app for sign in and enabled linkedin on settings with client ID and secret. Following is the code snippet i am using to try sign in

const { user, session, error } = await supabase.auth.signIn({
  provider: 'LinkedIn'
})

I am getting this -

{"code":400,"msg":"Unsupported provider: Provider is not enabled"}

Any one knows how to resolve this issue?

OK a couple reports now.... Also what region is your instance? Two other reports this morning: https://discord.com/channels/839993398554656828/990268349592248360

ap-south-1

Interesting... https://github.com/supabase/supabase/discussions/7402 Mumbai? This user had same message with "India" instance and when he switched it worked...

I'm currently using a Frontend Framework such as Sveltekit to read data during server-side rendering from Supabase. Is it a good practice to do that directly in the frontend? Or would you rather call an API and within your API you do all the Supabase access?

Hey there. I'm still somewhat new to Supabase so hopefully someone can confirm, but I think I can say this is what Supabase is designed for. When you created your database, you were given two access keys, which you can view under

Settings -> API

. The one called

anon / public

says "This key is safe to use in a browser if you have enabled Row Level Security for your tables and configured policies." It looks like the idea is that in order to gain access to any data in your database, a user would have to have the ANON key as well as a valid JWT issued by Supabase. So you won't have a security issue unless your application is open to XSS, etc, which could cause a user's valid login token to leak to other systems.