create-t3-turbo VS next-auth

Check out this starter repo https://github.com/t3-oss/create-t3-turbo I didn’t use it because it didn’t really fit my needs but it I’ve heard good things about it. May work for you

You can checkout https://github.com/t3-oss/create-t3-turbo which is based on https://create.t3.gg

t3-oss/create-t3-turbo: Clean and simple starter repo using the T3 Stack along with Expo React Native (github.com)

I don't have experience with this personally, but create-t3-turbo might be useful for you if this is something you want to do.

https://github.com/t3-oss/create-t3-turbo is a great repo for getting started quickly and seeing the advantages of exactly this.

I’ve been using a monorepo from the create-t3-turbo that uses pnpm and I haven’t had any issues so far.

create-t3-turbo is an amazing example of a turborepo setup done right, im always referencing it for how Julius (the creator) has things setup.

Coming back to your question, for development velocity the best option would be: Trpc + next.js + react native(Instead of flutter) in a turborepo. Look into this https://github.com/t3-oss/create-t3-turbo

create-t3-turbo is an excellent starting point IMO. There are forks of it that include things like Solito, Clerk (for authentication) and others. It does leverage tRPC quite heavily, but if your API is malleable enough to work with it, it really helps simplify everything for your shared API logic.

Understood. Can I swap out next trpc and plug in express trpc? I'm using T3 monorepo https://github.com/t3-oss/create-t3-turbo

NextAuth.js is not perfect. One of the shortcomings is that it currently does not implement federated logout. This means that even if a user signs out of the Next.js app, he does NOT get signed out of the Cognito user pool client. As a consequence, the user is not really being logged out (i.e he is able to login again without providing the credentials). You can read more about this problem in this Github thread.

NextAuth for adding auth

Let's learn a bit about Descope and how to use it with Auth.js (next-auth) to protect our Next.js app with role-based access control (RBAC).

https://github.com/nextauthjs/next-auth/issues/5647#issuecom...

Next Auth CognitoProvider Internal Library: https://github.com/nextauthjs/next-auth/blob/v4/packages/next-auth/src/providers/cognito.ts

I mentioned this in an age-old discussion on NextAuth GitHub repo.

Authentication is a fundamental part of most web applications. Integrating authentication into your Next.js app can be simplified with NextAuth, a powerful authentication library that supports various authentication methods. However, the documentation around setting up NextAuth with the "Credentials" auth provider might not be as clear as you'd hope. My implementation is greatly enriched and partially based on Next-Auth docs and the following github thread.

For Auth: https://authjs.dev/ - works like a charm with Svelte https://authjs.dev/reference/sveltekit

NextAuth.js

I'm surprised nobody mentioned https://authjs.dev/