import { NextResponse } from 'next/server'
import type { NextRequest } from 'next/server'

export function middleware(request: NextRequest) {
    const requestHeaders = new Headers(request.headers)
    requestHeaders.set('x-pathname', request.nextUrl.pathname)
    const response = NextResponse.next({
        request: {
            // New request headers
            headers: requestHeaders,
        },
    })
    return response
}

export const config = {
    matcher: [
        /*
         * Match all request paths except for the ones starting with:
         * - api (API routes)
         * - _next/static (static files)
         * - _next/image (image optimization files)
         * - favicon.ico (favicon file)
         */
        '/((?!api|_next/static|_next/image|favicon.ico).*)',
    ],
}

this is the most recent change i have made

okay show me the console in vs code

keep the console open and refresh

I did refresh but i dont see any new logs in the terminal

in the browser

there should be a bunch of react errors

when you refresh

its fixed?

no

like i said in local machine i dont see any error

only after deploying to vercel i see the error and the error message aint helpful at all

in local machine it works but in vercel it shows the error?

yes

forget local machine, show me vercel logs

this is the most recent change

const pathname = headersList.get("next-url")

from this ^ i have added the middleware and changed it to

const pathname = headersList.get("x-pathname")

dont see anythink wrong in there

are there other logs, other then api logs

no

try rebuild

is there any way to get full error message in vercel ?

never used vercel for hosting so i cant really tell you,

try to rebuild the project

yeah rebuilding

most likely wont fix it ill do some digging

https://github.com/coding-club-gct/blogs
repo if you would like to see 🙂

rebuild completed, verfied it in private window still the same issue

damn :(

did you read this
https://stackoverflow.com/questions/72607999/next-js-application-error-a-client-side-exception-has-occurred-see-the-browser

i know its frosturating but dont give up, eventually you will fix it

yeah, i have to do some really annoying if statements and deploy each time

in your local machine, try this
npm run build npm run start

i think i can do this, but its frustrating :(

and see if the error happens there

as this error happens in production, not development, you run npm run build to build the production files, then npm run start

yeah like i said production mode in local machine works fine

no error

thats odd

i got this error

check where you have perfomed .auth

this error happens when trayng to access a null object

in your case e is undefined

i navigate to how to blog

oh

btw hello ray, hope you had a nice day

 const { name, blog, html_url, email } = await getProfileFromUsername(author.login)
    const { name: committerName } = await getProfileFromUsername(committer.login)

i think the error come from here

yeah i can see the error message in chrome as well

damn firefox and chrome giving different error messages

you too 😀

my day was mid, could for the love of me, not get data revalidation to work

revalidation something is a little bit tricky for now 😆

then i tried router.reload

guess what it didnt work

if i had to track the time i spend, 99% is bug fixing

apparently something is getting messed up with the Link component

i have replaced all the Link with <></> and now its working

what were you using link for?

i get few urls from github api and print it in the page

with link tag

glad to be of help, even if it was 1%, mark this as solved

yes, thank you as well

you're welcome

you can also close the post,