Why does Next.js 14 fail to resolve page route paths?

Question

I'm encountering an issue with my Next.js project where I'm receiving the error message: "You cannot have two parallel pages that resolve to the same path." It specifically references /(landing)/page and /(main)/(routes)/(documents)/page. I've checked the route group documentation provided by Next.js, but I'm still unclear on how to resolve this issue effectively. Could you please provide guidance on how to address this error and ensure proper routing in my Next.js application?

I attempted to define routes in Next.js 14 but encountered unresolved paths for pages. I expected the routes to map correctly to their respective pages, but actual results showed unresolved paths.

Youssouf Oumar · Accepted Answer · 2024-02-23 09:25:48Z

3

Since route groups, aka the folders with (...) are not taken into consideration when resolving path, app/(landing)/page.js and app/(main)/(routes)/(documents)/page.js will match / as it's like you had tow app/page.js, creating a conflict.

So you have to decide which one should render when / is requested. If it's app/(landing)/page.js, you should change app/(main)/(routes)/(documents)/page.js to something like app/(main)/(routes)/(documents)/about/page.js, so it matches /about.

answered Feb 23, 2024 at 9:25

Youssouf Oumar

47.5k16 gold badges109 silver badges108 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

Why does Next.js 14 fail to resolve page route paths?

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related