Next.js Discord

Discord Forum

Client-Side exception occur after build in vercel deployment

Unanswered
Crazy ant posted this in #help-forum
Open in Discord
Crazy antOP
this is happen everytime after i update to nextjs 13.4.13, in my local machine, everythings does working fine, build and then open /blogs/[slug] route. but after i build in vercel, accessing /blogs/[slug] route for the first time always occur this client-side exception, after refresh, then it does render the page. the stack is not helping at all, why tho?

14 Replies

looks like a nextjs bug
@joulev does the same thing happen if you upgrade or downgrade nextjs version?
Crazy antOP
before i use 13.4.13, it does working fine
joulev
then it is a nextjs bug indeed.
1. downgrade to the last working version
2. browse the [bug tracker](https://github.com/vercel/next.js/issues) to check if someone already reported this; if no one has reported this then please make a bug report
Crazy antOP
this is in my /blogs/[slug] route, it is working fine in dev and build in my local, error only occur after build in vercel, then open the route for first time, i guess this is problem with opt caching?
joulev
i don't see any issues with your code, definitely a nextjs bug, please make a report if there isn't one already
13.4.13 is very buggy imo, i also haven't been able to upgrade, my company app is still at 13.4.12
Crazy antOP
alright, yeah probably some changes got me the error
Crazy antOP
@joulev update: i found out what component that causing the error, it was Image component from "next/image", i update nextjs and using Image in my /blogs/[slug] route, after build it causes that client-side exception, but after i change it to regular intrinsic <img> elements, i never got that error again
since you're the only one paying attention to my forum post here, so i tag you, sorry if it's bothering but could you help me out to reach this discussion to official team?
Asian black bear
@Crazy ant Does it only fail on mobile devices, or is it everywhere?
i could confirm this after i switching twice between using Image component and <img>, it does only happen when i use Image from "next/image"
@Crazy ant since you're the only one paying attention to my forum post here, so i tag you, sorry if it's bothering but could you help me out to reach this discussion to official team?
joulev
i can't do that because i don't have a reproduction and even if i had, i would not have a faster route to report bugs than the general route of making a bug report; so please, make a reproduction and submit a bug report