ahkhanjani Comments - Answer Overflow

I did not include that because I'm not sure if it should be in the readme since it might be a auth.js bug. But I do think it should be in the code itself for now. I'll leave that to @julius to decide. Here's my PR: https://github.com/t3-oss/create-t3-turbo/pull/914/files#diff-d3db73f679dc5776a7bc9ebd6f10fbb751898e2cab3e33861196b35126476a65

11 replies

TTCTheo's Typesafe Cult

•Created by ahkhanjani on 3/10/2024 in #questions

Nitro, Next Auth and Google callback URL

I made a PR but left this part out since it's not really relevant to the project itself as it doesn't have any options for discord

11 replies

TTCTheo's Typesafe Cult

•Created by ahkhanjani on 3/10/2024 in #questions

Nitro, Next Auth and Google callback URL

If the provider in your main project has some options like scope or other things, create a file called packages/auth/src/options.ts and export the options and use it in both projects to get the same behavior everywhere.

11 replies

TTCTheo's Typesafe Cult

•Created by ahkhanjani on 3/10/2024 in #questions

Nitro, Next Auth and Google callback URL

It's totally inferring them. At least I assume so the entire process is working just fine. I couldn't find anything on them being optional or required. The docs are a joke

11 replies

TTCTheo's Typesafe Cult

•Created by ahkhanjani on 3/10/2024 in #questions

Nitro, Next Auth and Google callback URL

Let me figure out why mine is working without them then 🥲

11 replies

TTCTheo's Typesafe Cult

•Created by ahkhanjani on 3/10/2024 in #questions

Nitro, Next Auth and Google callback URL

Also with next-auth v5, manually passing provider variables to Discord() or Google() etc. isn't required

11 replies

TTCTheo's Typesafe Cult

•Created by ahkhanjani on 3/10/2024 in #questions

Nitro, Next Auth and Google callback URL

Figured it out. If you're using a subdomain for the auth-proxy project, e.g. auth.yourdomain.com, add this callback URL to Google Cloud dashboard: https://auth.yourdomain.com/callback/google (as you can see there's no /api/auth/). Then since there's a bug (?) in next-auth v5 beta right now (https://github.com/nextauthjs/next-auth/discussions/9748), set basePath: "/" in auth-proxy Auth options so that it won't default to /api/auth/. If the provider in your main project has some options like scope or other things, create a file called packages/auth/src/options.ts and export the options and use it in both projects to get the same behavior everywhere.

11 replies

TTCTheo's Typesafe Cult

•Created by ahkhanjani on 3/7/2024 in #questions

uploadthing: What happens when file name already exists?

So... we get a duplicate entry

3 replies

TTCTheo's Typesafe Cult

•Created by Arxk on 2/21/2024 in #questions

Retrieving metadata from uploadFiles

Good question

2 replies

TTCTheo's Typesafe Cult

•Created by ahkhanjani on 2/26/2024 in #questions

Next-auth v5 config file server code leaks into client components

Solved by importing singIn() from next-auth/react like before in /pages

2 replies

Gaming

Programming