Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Failed to load the correct optional catch all route (9.5.4)

See original GitHub issue

Bug report

Describe the bug

There are two routes in our project

[destintionName]/[[...params]] - DestinationPage
[desitntionName]/properties/[propertyId]/package/[[...params]] - PackagePage

To Reproduce

Steps to reproduce the behavior, please provide code snippets or a repository:

On DestinationPage /cairns
Click <Link href="/cairns/properties/123451/package" /> to go to PackagePage
It updates browser url to /cairns/properties/123451/package

Expected behavior

Expects to go and load PackagePage, but it refreshes and load DestinationPage

It works on 9.5.3

System information

OS: macOS
Browser (if applies) chrome
Version of Next.js: 9.5.4
Version of Node.js: 10.16.3

Issue Analytics

State:
Created 3 years ago
Reactions:1
Comments:5 (4 by maintainers)

Top GitHub Comments

1reaction

ijjkcommented, Dec 30, 2020

Hi, this appears to be working as expected on the latest canary of Next.js v10.0.5-canary.3, please update and give it a try!

1reaction

ijjkcommented, Oct 12, 2020

Thanks for the reproduction, it looks like this is from a conflict with the basePath config and the automatic href resolving.

To get around this for now you should be able to use the manual href and as logic previously used for dynamic routes e.g. href="/[destinationName]/properties/[propertyId]/package" as="/cairns/properties/413969/package"