what if you do return NextResponse.redirect(...)?

i feel like redirect() doesn't work sometimes, behaviour like you described has also been reported elsewhere in this server, it's a bug

So what can be an alternative?

Maybe using redirect from the client side??

have you tried this? this is the alternative i suggest

It changes nothing!

Even docs also mention that return is not required when using redirect 🤷‍♂️

yeah redirect and NextResponse.redirect are different functions and have different usage but should do the same thing

wait

how do you fetch the api route?

fetch("/api/auth")?

if so, redirecting inside the api route itself will do nothing because it will just become fetch("/persons")

you have to use client-side useRouter to reach a new route

or use server actions instead where redirect works for your use case

So actually how can I write the redirects app level

Like if user is logged in already and trying to access auth routes it should get redirected to home.
And when not authenticated & accessing protected routes it should get redirected to auth route/page.

I'm looking for a generic approach ( app level config thingy ) rather having similar code pieces/logic everywhere.

If you have a code example maybe a repo or similar that will be super cool.

so the bad news is, there is no single best way to do it. different libraries have different approaches. different people prefer different things. and if you bring your own auth, depending on how you implement it you might need different ways to do it.

but here are some common methods:
* redirect in middleware
* redirect via client-side rendering
* whenever you render protected data in a server component, you check authentication and if auth doesn't pass, you redirect