Middleware issue

[prime willow]

anyone ?

[chrome arrow]

it looks good to me

does this happen on production or development mode?

[prime willow]

both

[chrome arrow]

does your conditional statement work?

If you add a console.log will it execute it?

[prime willow]

yup

[chrome arrow]

I have almost the same issue, but for me it works fine in development but not in production

[chrome arrow]

try installing the canary version of next.js where have a lot of bugs fixed npm install next@canary

[prime willow]

wait I found that home route is not matching

I have the lang in pathname for exemple /en | /fr | /de

[chrome arrow]

Ye I see with next-translate

[prime willow]

should I add each to protectedPaths array ?

[prime willow]

https://www.npmjs.com/package/next-intl

[chrome arrow]

translation prefixes are not be part of pathname I think

[chrome arrow]

so no

[prime willow]

I added a console.log to display the pathname it prints this "/en"

[chrome arrow]

ok..

[chrome arrow]

but its not a neat way

[prime willow]

I agree

do you have another solution ?

[chrome arrow]

No sorry idk

Can you help me with my code?

export async function middleware(request) {
    const cookie = request.cookies.get("token")?.value;

    if (request.nextUrl.pathname === "/" && cookie) {
        return NextResponse.redirect(new URL("/home", request.url));
    }
}

Im not using next-auth, should I use it

[prime willow]

Create a ticket I'll answer you there 😄

[chrome arrow]

I don't know if these are good manners, help then ask for help xd

https://discord.com/channels/752553802359505017/1097642966719402004

Why do you use url.searchParams.set("callbackUrl", pathname); ?

[prime willow]

to keep the callback in the url

[chrome arrow]

ok