You beauty. Been a VueJs dev for a time, lack of western contracts though. Currently learning NextJS. Dont want to give up on supabase. This is just what i needed...
@@adrianfam8098 nuxt / vue is awesome. IF you are rolling your own - it cant be beat. React can be very verbose compared to vue. Its so much easier to keep on top of too.
This is fantastic, but what if I want to make a request to an internal API that uses Supabase authentication to protect routes? I would need the session to obtain the user’s token, but all the documentation states that getSession is no longer recommended. Also, thank you for the excellent videos!
This template uses the SSR package under the hood, which configures Supabase Auth to use cookies. This means the Supabase Client will be automatically configured to use the user's session. If the "internal API" is outside your Next.js app, and you're making a HTTP request to it, you just need to send along the headers from Next.js to the HTTP request - check out the `utils/supabase/server` file to see an example of creating a Supabase Client using the cookies function! This example is just showing how you might want to enforce those Authorization rules or protect entire pages in Next.js 👍
@@JonMeyers Thanks for the clear explanation! We’re in the process of migrating our stack to use Supabase, and I’m really enjoying the experience so far
It's good but you can do MUCH better. Maybe a CLI to generate an entire app well configured and up to date with latest next.js, ORM(prisma), social auth (google, github), emails with react-email and resend, posthog, sentry, eslint, prettier... The CLI would give the choice to choose if we want the tool included or not. If you want to go even further you can have one for a a next.js app and another one for a chrome extension. I know it needs to be maintained, but I think it's worth it. The current one doesn't do much imo, a little bit useless / outdated and not using the best possible code.
you do that put a stripe in between market it like marc lou and shashing. lol. you know you have that problem maybe other don't but maybe for supabase guys it's not a business case they have other task that have more long term value for their project.
Yeah, this is definitely just a starter template - get the config out of the way so you can build whatever you like. For a more complete SaaS starter, you could check out this one: github.com/vercel/nextjs-subscription-payments/
Get started with Next.js 15 and Supabase 👉 database.new
Do you have an example where you're using MFA and Supabase Auth (not an alternative auth provider) ?
Awesome video. You guys make this stuff so simple.
Supabase in the wild! 🌿
Its the new Outdoor API from Next.js 15! Looks great!
Good video. Interested in the video where said you will show how to connect custom SMTP.
Working on this one now - will let you know when it's live! 👍
@@JonMeyers thanks!
You beauty. Been a VueJs dev for a time, lack of western contracts though. Currently learning NextJS. Dont want to give up on supabase. This is just what i needed...
Dang, I «know» next js but currently looking into vue/nuxt… will I regret it?
@@adrianfam8098 nuxt / vue is awesome. IF you are rolling your own - it cant be beat. React can be very verbose compared to vue. Its so much easier to keep on top of too.
Great to hear! Let me know if you hit any friction points!
@@adrianfam8098 They're both awesome! And work perfectly with Supabase!
can I safely call await createClient multiple times or should I store a singleton?
Thanks for tutorial. Super helpfull
is it better to protect pages in middleware or like in the example in video?
Better practice to protect them in Middleware, as this allows you to redirect unauthenticated users in that very first step 👍
This is fantastic, but what if I want to make a request to an internal API that uses Supabase authentication to protect routes? I would need the session to obtain the user’s token, but all the documentation states that getSession is no longer recommended.
Also, thank you for the excellent videos!
This template uses the SSR package under the hood, which configures Supabase Auth to use cookies. This means the Supabase Client will be automatically configured to use the user's session. If the "internal API" is outside your Next.js app, and you're making a HTTP request to it, you just need to send along the headers from Next.js to the HTTP request - check out the `utils/supabase/server` file to see an example of creating a Supabase Client using the cookies function!
This example is just showing how you might want to enforce those Authorization rules or protect entire pages in Next.js 👍
@@JonMeyers Thanks for the clear explanation! We’re in the process of migrating our stack to use Supabase, and I’m really enjoying the experience so far
Thanks you please make samedi with supabase and JavaScript vanilla
for maybeGlobalAsyncLocalStorage eror.... ``` "next": "^14.0.0",```
BIG!
So big!
the saas template doesn’t work when following the guide and video
Oh yeah, good call! This one still needs to be updated for Next.js 15! Will get that sorted! 🙌
It's good but you can do MUCH better.
Maybe a CLI to generate an entire app well configured and up to date with latest next.js, ORM(prisma), social auth (google, github), emails with react-email and resend, posthog, sentry, eslint, prettier...
The CLI would give the choice to choose if we want the tool included or not.
If you want to go even further you can have one for a a next.js app and another one for a chrome extension.
I know it needs to be maintained, but I think it's worth it.
The current one doesn't do much imo, a little bit useless / outdated and not using the best possible code.
you do that put a stripe in between market it like marc lou and shashing. lol. you know you have that problem maybe other don't but maybe for supabase guys it's not a business case they have other task that have more long term value for their project.
also they are a yc company if my memory is good and their investor do not pay them to try too crazy idea that are out of the focus of their mission
Yeah, this is definitely just a starter template - get the config out of the way so you can build whatever you like. For a more complete SaaS starter, you could check out this one: github.com/vercel/nextjs-subscription-payments/
supabase + create-t3-app
Fastest🎉 comment of this video
Wow!
Fastest reply! ⚡
second fastest comment in here 🚀🚀🚀🚀🚀🚀
Smashed it! 🚀
LFG
Your hands are doing too much. Relax.