Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug: Parallel intercepted route in Next.js #11587

Open
Cussone opened this issue May 11, 2024 · 0 comments
Open

Bug: Parallel intercepted route in Next.js #11587

Cussone opened this issue May 11, 2024 · 0 comments

Comments

@Cussone
Copy link

Cussone commented 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.

@Cussone Cussone changed the title Issue with parallel intercepted route in Next.js Bug: Parallel intercepted route in Next.js May 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant