You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a Next.js application with a parallel intercepted route. I am catching a certain route and rendering a modal over the current route.
When deployed to Vercel there is an issue when opening that route. The code is working perfectly fine locally in both, development and production mode.
Here is the error I am getting: Application error: a client-side exception has occurred (see the browser console for more information).
I found out that on Vercel deployment the page param for the [collection] path gets logged as %5Bcollection%5D inside the modal, which is most likely causing the error. [collection] is the folder name, it should be logging the appropriate part of the path from the URL and not the literal folder name.
If anything else is needed from my side, I will gladly help. Hopefully, I was clear enough.
The text was updated successfully, but these errors were encountered:
Cussone
changed the title
Issue with parallel intercepted route in Next.js
Bug: Parallel intercepted route in Next.js
May 11, 2024
I have a Next.js application with a parallel intercepted route. I am catching a certain route and rendering a modal over the current route.
When deployed to Vercel there is an issue when opening that route. The code is working perfectly fine locally in both, development and production mode.
Here is the error I am getting:
Application error: a client-side exception has occurred (see the browser console for more information).
I made a repository with an example: https://github.com/Cussone/vercel-nextjs-routing-bug
And here is the deployment: https://vercel-nextjs-routing-bug.vercel.app/en
I found out that on Vercel deployment the page param for the
[collection]
path gets logged as%5Bcollection%5D
inside the modal, which is most likely causing the error.[collection]
is the folder name, it should be logging the appropriate part of the path from the URL and not the literal folder name.If anything else is needed from my side, I will gladly help. Hopefully, I was clear enough.
The text was updated successfully, but these errors were encountered: