Next 13.4 Error: NEXT_REDIRECT in API routes

My /app/api/auth/route.ts file:

import { redirect } from 'next/navigation';

export async function GET(req: Request) {
  try {
    redirect('/dashboard');
  } catch (error) {
    console.log(error);
    redirect('/');
  }
}

I realized that when I do redirect in a try catch, I get the error :

Error: NEXT_REDIRECT
    at getRedirectError (webpack-internal:///(sc_server)/./node_modules/next/dist/client/components/redirect.js:40:19)
    at redirect (webpack-internal:///(sc_server)/./node_modules/next/dist/client/components/redirect.js:46:11)
    at GET (webpack-internal:///(sc_server)/./app/api/auth/route.ts:23:66)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async eval (webpack-internal:///(sc_server)/./node_modules/next/dist/server/future/route-modules/app-route/module.js:244:37) {
  digest: 'NEXT_REDIRECT;replace;/dashboard'
}

When I get get rid of the try catch everything works fine:

export async function GET(req: Request) {
  redirect('/dashboard')
}

This works as expected. I need try and catch because this is an auth route and I need some error handling because the request could fail, I have left out the auth functionalities becuase I realized that this happens just on a simple try and catch.

Or if Next 13 has another way of error handling in /api routes please let me know.

At the moment, the workaround I found is to not use:

import { redirect } from 'next/navigation';

But to use instead:

import { useRouter } from 'next/navigation'
const router = useRouter()
router.push("/")

This is because internally, redirect() is throwing an Error.
See https://github.com/vercel/next.js/blob/canary/packages/next/src/client/components/redirect.ts#L16-L41C2

use
return NextResponse.redirect(new URL('/home', request.url))

in next 13+ app dir server side

Its easy to fix it. currently there is a bug in try catch block with next redirect. but you dont need to chancge anything. you just need to transfer try, cath block in different function thats it. i give you example of my code

"use server"
import LoginSchema from "@/Schemas/LoginSchema";
import PocketBase from 'pocketbase';
import { redirect } from 'next/navigation'

const analyze = async(data) =>{
    const pb = new PocketBase('http://127.0.0.1:8090');
    try{
        const authData = await pb.collection('UserTable').authWithPassword(await data.Email, await data.Password);
        if (authData){
            return authData
        }
    }
    catch(error){
        error
    }
}

export async function LoginAction(data) {
    const result = await LoginSchema.isValid(await data)
    if (result === true) {
        const result = await analyze(data)
        if(result){
            return redirect("/")
        }
        else{
            return "failed"
        }
        
    }
    else {
        return "failed"
    }

}

The error that I got was Uncaught (in promise) Error: NEXT_REDIRECT

And I'm not sure if this is a bug... Because the method needs context info that is available inside "react render time!".

So this will work if you create a reference to use it later.

import { useRouter } from 'next/navigation'

function reactFunctionComponent() {
  const router = useRouter()
  runWithPromise().then( () => router.push("/") )
  ...
}

More info

This happened to me when I used a try...catch statement. Rewrote my code in a way that didn't need a try...catch statement and it now works fine. This doesn't necessarily happen to API route files only, could happen in a react component where redirect is called inside a try catch.