Great content as always Hamed ! I would love the clerk course to cover all the advanced topics especially organizations and all there aspects, as most of youtube tutos stick to basic sign-in and signup topics
@@ryujinwatatsumi I'm working with the Clerk team on this actively and I'm hoping to get it done in the next 8-12 weeks. Join the waitlist to I can notify you with the progress.
Well done Hamed 👏on adding Roles, Permissions and Multi Tenant to your Clerk course, most You Tubers would just skip this key part of most b2b solutions.
I really hope one day you make a video on Clerk (as one of the most popular auth platoforms, if not the most popular) vs. next-intl (probably the most popular internationalization platform for next.js) I could never fully resolve middleware clash betwen those two and could find the solution on the internet. Including translations from API (or other server solution... not just static .json files), including Clerk components, like buttons and profiles collapse when turning on translations. You have one of the most professional resources on the topic I have ever seen, so who would do it if not you 🙏
Great video! Unfourtanetley I am getting "Error: Clerk: The "/signup" route is not a catch-all route. It is recommended to convert this route to a catch-all route, eg: "/signup/[[...rest]]/page.tsx". Alternatively, update the SignUp component to use hash-based routing by setting the "routing" prop to "hash". " Even though I have exactly the same structure as it's suggested in the error. Have you ever encountered this?
Hmm 🤔 I haven't had this problem, make sure the path is `app/sign-up/[[...sign-up]]/page.tsx` and that you've added the env variables `NEXT_PUBLIC_CLERK_SIGN_UP_URL=/sign-up`. You can also clone my code and compare it to yours.
For `beforeAuth` you can do what you need inside the `clerkMiddleware` before you call the `auth().protect()` function. For the `afterAuth` you can return the next middleware function from your `clerkMiddleware`.
Hi, great video, but I am trying to deploy a nextjs + clerk app and the sign in redirect url remains as 127.0.0.1 ... i have searched high and low, gone thru documentation several times, messaged the dev team with no avail, maybe u or someone here can help :( .. thanks in advance
Do you have custom sign-in and sign-up page? If you do, you need to set the following environment variables; also check the variables you're setting in your production deployment. ``` NEXT_PUBLIC_CLERK_SIGN_IN_URL=/sign-in NEXT_PUBLIC_CLERK_SIGN_UP_URL=/sign-up ```
I just cloned your repo and noticed that you have the SignInButton as a mode='modal'. That means you are not using the sign-in page. Was that intentional? Do you recommend that?
found this in the discussions on the github. it cannot be solved. you have to move provider deeper or do something else. its buggy and brittle unfortunately, cant work for me =(
@@hamedbahram With a package like Auth.js it is definitely one of the easier features to implement in your app. Very easy to set up and gives you more than enough out of the box for most apps in my opinion. I guess the point for me is that if I'm going to spend money to make my development process easier, auth is not anywhere near the top of the list. Clerk are great marketers though.
@@franklinmayoyo I'm sure there are some valid use cases for it. Just be aware of the downsides. It is potentially expensive, there are concerns about the user data, and you are also outsourcing a very important part of your app to a third party. Who knows where Clerk will be in a year or two.
@@franklinmayoyo I would also take the word of RUclips "techfluencers" with a massive grain of salt. Clerk is not afraid to spend money on advertising.
Great video Hamed 👏 I work at Clerk and this is spot-on!
Cool, thanks Alex! I appreciate that.
it's so much easier and bug free than prior version
Absolutely!
Thanks Hamed appreciate that
My pleasure!
Great content as always Hamed ! I would love the clerk course to cover all the advanced topics especially organizations and all there aspects, as most of youtube tutos stick to basic sign-in and signup topics
My pleasure! Absolutely, I'm exciting for the course as well.
@@hamedbahram when will the course drop ?
@@ryujinwatatsumi I'm working with the Clerk team on this actively and I'm hoping to get it done in the next 8-12 weeks. Join the waitlist to I can notify you with the progress.
Well done Hamed 👏on adding Roles, Permissions and Multi Tenant to your Clerk course, most You Tubers would just skip this key part of most b2b solutions.
@@nelco63 Thanks! Agreed!
I really hope one day you make a video on Clerk (as one of the most popular auth platoforms, if not the most popular) vs. next-intl (probably the most popular internationalization platform for next.js) I could never fully resolve middleware clash betwen those two and could find the solution on the internet. Including translations from API (or other server solution... not just static .json files), including Clerk components, like buttons and profiles collapse when turning on translations. You have one of the most professional resources on the topic I have ever seen, so who would do it if not you 🙏
Thanks for the kind words and the suggestion, I'll definitely have that in the Clerk course, but maybe even here on RUclips.
Great video! Unfourtanetley I am getting "Error: Clerk: The "/signup" route is not a catch-all route. It is recommended to convert this route to a catch-all route, eg: "/signup/[[...rest]]/page.tsx". Alternatively, update the SignUp component to use hash-based routing by setting the "routing" prop to "hash". "
Even though I have exactly the same structure as it's suggested in the error. Have you ever encountered this?
Hmm 🤔 I haven't had this problem, make sure the path is `app/sign-up/[[...sign-up]]/page.tsx` and that you've added the env variables `NEXT_PUBLIC_CLERK_SIGN_UP_URL=/sign-up`. You can also clone my code and compare it to yours.
Is it possible to create a custom signup page with a role based section like
consult or bussniess for example where consult is checked in by default?
Of course!
why clerk is not working with expo react native
Not sure on that end, I'd reach out to Clerk's support.
what about beforeAuth and afterAuth is there any alternative ?
For `beforeAuth` you can do what you need inside the `clerkMiddleware` before you call the `auth().protect()` function. For the `afterAuth` you can return the next middleware function from your `clerkMiddleware`.
Hi, great video, but I am trying to deploy a nextjs + clerk app and the sign in redirect url remains as 127.0.0.1 ... i have searched high and low, gone thru documentation several times, messaged the dev team with no avail, maybe u or someone here can help :( .. thanks in advance
Do you have custom sign-in and sign-up page? If you do, you need to set the following environment variables; also check the variables you're setting in your production deployment.
```
NEXT_PUBLIC_CLERK_SIGN_IN_URL=/sign-in
NEXT_PUBLIC_CLERK_SIGN_UP_URL=/sign-up
```
I just cloned your repo and noticed that you have the SignInButton as a mode='modal'. That means you are not using the sign-in page. Was that intentional? Do you recommend that?
It's just a matter of preference, whether you like to redirect the user to the sign-in page or just show them a modal without switching context.
@@hamedbahram ygkk kk
Try calling the api route '/api/me' on a server page using fetch . The userId always returns null
why would you call the api route from a server page? but for whatever reason you do, you have to pass the headers to the fetch function.
hello Hamed. Can you tell me that how can I track talk time of user in minutes using clerk metadata?
Watch this video where I used Clerk metadata to track user credits → ruclips.net/video/vi9VhhMFpWI/видео.html
Thank you, appeciate that.
My pleasure!
wrapping your layout with making all routes in your project dynamic. Is there way to prevent this?
found this in the discussions on the github. it cannot be solved. you have to move provider deeper or do something else. its buggy and brittle
unfortunately, cant work for me =(
actually..... it is somehow can be done not great DX though
@@27sosite73 Doesnt that turn your hole app into client side?
nope!
Thanks for flagging this. I'm talking to the Clerk team, trying to figure out why this is.
how can we change font of the export default and return in the vs code
anyone guide me how can we do this type in my vs code
Use a theme that supports italics.
@@hamedbahram Which theme are you using in your vs code for this?
@@CodeMonsterOfficial "Dark+ Italics"
I can't for the life of me figure out why you'd want to pay for something as basic as auth.
It's great that you find authentication easy!
@@hamedbahram With a package like Auth.js it is definitely one of the easier features to implement in your app. Very easy to set up and gives you more than enough out of the box for most apps in my opinion. I guess the point for me is that if I'm going to spend money to make my development process easier, auth is not anywhere near the top of the list. Clerk are great marketers though.
It's helpful for users who need to ship fast and validate ideas.
@@franklinmayoyo I'm sure there are some valid use cases for it. Just be aware of the downsides. It is potentially expensive, there are concerns about the user data, and you are also outsourcing a very important part of your app to a third party. Who knows where Clerk will be in a year or two.
@@franklinmayoyo I would also take the word of RUclips "techfluencers" with a massive grain of salt. Clerk is not afraid to spend money on advertising.